Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c532caaf7c31a21cdc44952892007a7823f7b0af41b3d3d816ab8223c0e7671

Tx prefix hash: ce28d240dcf912ff5502223d53d619230727d73d0c5f4264f4d878ba75750f80
Tx public key: beef24a7c3f90c6e237b100ce8a9f764c548e12ee70a556fdcb486991e845f25
Timestamp: 1672142180 Timestamp [UCT]: 2022-12-27 11:56:20 Age [y:d:h:m:s]: 02:032:02:09:30
Block: 661666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544615 RingCT/type: yes/0
Extra: 01beef24a7c3f90c6e237b100ce8a9f764c548e12ee70a556fdcb486991e845f2502110000000133af99f4000000000000000000

1 output(s) for total of 3.941176103000 dcy

stealth address amount amount idx
00: 816510069f435f9d25a48e4793e8b91f6801ec5b645795fae577364850d969e8 3.941176103000 1102455 of 0

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": 661676, "vin": [ { "gen": { "height": 661666 } } ], "vout": [ { "amount": 3941176103, "target": { "key": "816510069f435f9d25a48e4793e8b91f6801ec5b645795fae577364850d969e8" } } ], "extra": [ 1, 190, 239, 36, 167, 195, 249, 12, 110, 35, 123, 16, 12, 232, 169, 247, 100, 197, 72, 225, 46, 231, 10, 85, 111, 220, 180, 134, 153, 30, 132, 95, 37, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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