Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f7ecea583a3ac9de084b75d561859aaf9902aeea86254e920ae408a8518b89

Tx prefix hash: 37a26f7e43b556452c294d2fd454046593d539007c12841e4639a5ddc3bd8d16
Tx public key: f9c2475e7cd3f631c4fd2b2ec45772605387fcfe3fef554b2f94ecc16b6984f6
Timestamp: 1722640014 Timestamp [UCT]: 2024-08-02 23:06:54 Age [y:d:h:m:s]: 00:307:04:10:56
Block: 1079437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219483 RingCT/type: yes/0
Extra: 01f9c2475e7cd3f631c4fd2b2ec45772605387fcfe3fef554b2f94ecc16b6984f602110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5b71e77ac54eab99e2fc32232c1a30413a038e675b640d1d40919376f7baaa6 0.600000000000 1552392 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": 1079447, "vin": [ { "gen": { "height": 1079437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5b71e77ac54eab99e2fc32232c1a30413a038e675b640d1d40919376f7baaa6" } } ], "extra": [ 1, 249, 194, 71, 94, 124, 211, 246, 49, 196, 253, 43, 46, 196, 87, 114, 96, 83, 135, 252, 254, 63, 239, 85, 75, 47, 148, 236, 193, 107, 105, 132, 246, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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