Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f8bf753255cce2cad4989bf3054b584da84ed2f25e86fa0755546d3d870687

Tx prefix hash: 7e755af88a642cc4b204ea2c7ef2e6993bf9d71d4f84a752d3e6e4e0a640f2bd
Tx public key: 0a35fa0d83fb49a6ec75e71bea9ca8875c0dc0693d680303c69af7949217aece
Timestamp: 1709157144 Timestamp [UCT]: 2024-02-28 21:52:24 Age [y:d:h:m:s]: 01:077:10:43:31
Block: 967662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316384 RingCT/type: yes/0
Extra: 010a35fa0d83fb49a6ec75e71bea9ca8875c0dc0693d680303c69af7949217aece0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0eaae8cbd38df87bf0b95c87c79fae91b1186affb1ccc8994f2d5de2f7ff594 0.600000000000 1427445 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": 967672, "vin": [ { "gen": { "height": 967662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0eaae8cbd38df87bf0b95c87c79fae91b1186affb1ccc8994f2d5de2f7ff594" } } ], "extra": [ 1, 10, 53, 250, 13, 131, 251, 73, 166, 236, 117, 231, 27, 234, 156, 168, 135, 92, 13, 192, 105, 61, 104, 3, 3, 198, 154, 247, 148, 146, 23, 174, 206, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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