Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2125305c93c8fc775491afd49901480d186c44f9110ea985f3beeff3277afbd8

Tx prefix hash: 7b7a505370ca02237cd23e61cc2ca2ca1c11e91de8f360806e6438ddd0126011
Tx public key: 4e7e5b00cef0f4c460e1ec5bea65e6bc05371c860c3f7fb2e071a49639cc300c
Timestamp: 1709824636 Timestamp [UCT]: 2024-03-07 15:17:16 Age [y:d:h:m:s]: 01:007:00:41:44
Block: 973210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266020 RingCT/type: yes/0
Extra: 014e7e5b00cef0f4c460e1ec5bea65e6bc05371c860c3f7fb2e071a49639cc300c02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15af81d767316f2928b75f4734321c2cfdf239e056194d312dce0cd20073766c 0.600000000000 1433143 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": 973220, "vin": [ { "gen": { "height": 973210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15af81d767316f2928b75f4734321c2cfdf239e056194d312dce0cd20073766c" } } ], "extra": [ 1, 78, 126, 91, 0, 206, 240, 244, 196, 96, 225, 236, 91, 234, 101, 230, 188, 5, 55, 28, 134, 12, 63, 127, 178, 224, 113, 164, 150, 57, 204, 48, 12, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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