Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad6be8f0b021530a378752cdc89fb64daf1ce20a1315c9d8e8ebd1bacab59db

Tx prefix hash: 8f33f4f5b8df7cf5301feab513b42fa7dda297b7425b026a842c26ea7b4d8ace
Tx public key: 310fdd35674a6d07c66cccbcef308f1e3e7722fbc688e8b099ca1452238dfbfc
Timestamp: 1694182356 Timestamp [UCT]: 2023-09-08 14:12:36 Age [y:d:h:m:s]: 01:202:17:39:20
Block: 843697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405993 RingCT/type: yes/0
Extra: 01310fdd35674a6d07c66cccbcef308f1e3e7722fbc688e8b099ca1452238dfbfc021100000008faf35c9c000000000000000000

1 output(s) for total of 0.982837389000 dcy

stealth address amount amount idx
00: f1fe5e4ce5ce1d07ceb0313a8f198b51c174f5dc30f0a72d3c8cab3cf0aabf4a 0.982837389000 1296957 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": 843707, "vin": [ { "gen": { "height": 843697 } } ], "vout": [ { "amount": 982837389, "target": { "key": "f1fe5e4ce5ce1d07ceb0313a8f198b51c174f5dc30f0a72d3c8cab3cf0aabf4a" } } ], "extra": [ 1, 49, 15, 221, 53, 103, 74, 109, 7, 198, 108, 204, 188, 239, 48, 143, 30, 62, 119, 34, 251, 198, 136, 232, 176, 153, 202, 20, 82, 35, 141, 251, 252, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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