Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c488cefa0b36299e17d247c031118e9cdd3e75b3d1b386930a35f935c3ccf45

Tx prefix hash: 79fc604d8de33302d0a13c5fe000a58967d65431955b4f1485d0eeb5a109d68d
Tx public key: dfb814f630a8f1f708d2bb50bd6d11d3d70be1be3a3998521dfdbfa813bd42f2
Timestamp: 1743748719 Timestamp [UCT]: 2025-04-04 06:38:39 Age [y:d:h:m:s]: 00:218:20:11:04
Block: 1253951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154121 RingCT/type: yes/0
Extra: 01dfb814f630a8f1f708d2bb50bd6d11d3d70be1be3a3998521dfdbfa813bd42f20211000000164060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23bc90c1967342ab1d443e43cf950d3e3f3e927167bc7dd1403a2d7043c73c80 0.600000000000 1741032 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": 1253961, "vin": [ { "gen": { "height": 1253951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23bc90c1967342ab1d443e43cf950d3e3f3e927167bc7dd1403a2d7043c73c80" } } ], "extra": [ 1, 223, 184, 20, 246, 48, 168, 241, 247, 8, 210, 187, 80, 189, 109, 17, 211, 215, 11, 225, 190, 58, 57, 152, 82, 29, 253, 191, 168, 19, 189, 66, 242, 2, 17, 0, 0, 0, 22, 64, 96, 246, 210, 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