Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4a4590f361269d014f777684d3f65414967e21e6c2b4ac9870440233afed19

Tx prefix hash: 6967e7a567f79544aaea8c06f2acec3a23cea3438c837cc8dcc93cce47c6e07a
Tx public key: 6cc0c243f0bd925c562ac40f32a702978f816fb539664b215f4024b04f6ab5bd
Timestamp: 1728987988 Timestamp [UCT]: 2024-10-15 10:26:28 Age [y:d:h:m:s]: 00:181:10:12:35
Block: 1132071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129455 RingCT/type: yes/0
Extra: 016cc0c243f0bd925c562ac40f32a702978f816fb539664b215f4024b04f6ab5bd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4839660d8a7dbc395637715f3c4fa57047a0aad200d02b9231d42bb3c6927bc2 0.600000000000 1614982 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": 1132081, "vin": [ { "gen": { "height": 1132071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4839660d8a7dbc395637715f3c4fa57047a0aad200d02b9231d42bb3c6927bc2" } } ], "extra": [ 1, 108, 192, 194, 67, 240, 189, 146, 92, 86, 42, 196, 15, 50, 167, 2, 151, 143, 129, 111, 181, 57, 102, 75, 33, 95, 64, 36, 176, 79, 106, 181, 189, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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