Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f1cf80f4970689d01217d21b585e8b93e761e541cbbcf565ff6bf45bc2d8bf09

Tx prefix hash: 3fba51f6841802c3806ee24352a04b1959f856a35cca136eca67cd64a1d42e95
Tx public key: 3c33c1af99c45f7bf8b47feb4216e5583fb25df2b23e9f7fb41a7e3f36092bad
Timestamp: 1749886897 Timestamp [UCT]: 2025-06-14 07:41:37 Age [y:d:h:m:s]: 00:148:14:23:38
Block: 1304692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103965 RingCT/type: yes/0
Extra: 013c33c1af99c45f7bf8b47feb4216e5583fb25df2b23e9f7fb41a7e3f36092bad02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370c440de581e50d42ac4f4afe08351f60c15f331e4d4b49440e703b513034fc 0.600000000000 1792283 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1304702, "vin": [ { "gen": { "height": 1304692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370c440de581e50d42ac4f4afe08351f60c15f331e4d4b49440e703b513034fc" } } ], "extra": [ 1, 60, 51, 193, 175, 153, 196, 95, 123, 248, 180, 127, 235, 66, 22, 229, 88, 63, 178, 93, 242, 178, 62, 159, 127, 180, 26, 126, 63, 54, 9, 43, 173, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8