Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c878744b2ed0d7baba666e5f3979b0c77d72abd7b314527c1a6e4aeea59c008b

Tx prefix hash: f29a2e3419392f5a2c155fcf2ff680318eedae6b871edf3e61879900a85760bf
Tx public key: 637e6cabb8aa717f4b1d8d206cfc009f58699f8a65c58203f9a2005d65e01599
Timestamp: 1718485002 Timestamp [UCT]: 2024-06-15 20:56:42 Age [y:d:h:m:s]: 00:278:23:47:52
Block: 1045009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199353 RingCT/type: yes/0
Extra: 01637e6cabb8aa717f4b1d8d206cfc009f58699f8a65c58203f9a2005d65e01599021100000001b428b0c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 490042be1bb702e5b7b09ce0139b90097d918035ed8cc1fde5c11aa4fc79f73c 0.600000000000 1514470 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": 1045019, "vin": [ { "gen": { "height": 1045009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "490042be1bb702e5b7b09ce0139b90097d918035ed8cc1fde5c11aa4fc79f73c" } } ], "extra": [ 1, 99, 126, 108, 171, 184, 170, 113, 127, 75, 29, 141, 32, 108, 252, 0, 159, 88, 105, 159, 138, 101, 197, 130, 3, 249, 162, 0, 93, 101, 224, 21, 153, 2, 17, 0, 0, 0, 1, 180, 40, 176, 196, 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