Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2d7dfa848d72d7bd175760177393c3cdfbb718a4000094f0fb44e00dfded70

Tx prefix hash: 3d0a58c0e04661ff0f6787e93424cd61b933f94c72707fe662afdc2e372b6368
Tx public key: 6d8ae24957ee98512352cdc91b1ed6e25e1540b47563d9b67e584654ea249e80
Timestamp: 1706838153 Timestamp [UCT]: 2024-02-02 01:42:33 Age [y:d:h:m:s]: 00:305:17:53:55
Block: 948428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218914 RingCT/type: yes/0
Extra: 016d8ae24957ee98512352cdc91b1ed6e25e1540b47563d9b67e584654ea249e8002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f1f38b73600debdfb65f5c39ba7fbb72b340a4186c4ed90b0bab88d4856b6a 0.600000000000 1406834 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": 948438, "vin": [ { "gen": { "height": 948428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f1f38b73600debdfb65f5c39ba7fbb72b340a4186c4ed90b0bab88d4856b6a" } } ], "extra": [ 1, 109, 138, 226, 73, 87, 238, 152, 81, 35, 82, 205, 201, 27, 30, 214, 226, 94, 21, 64, 180, 117, 99, 217, 182, 126, 88, 70, 84, 234, 36, 158, 128, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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