Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 787b9b7b16ea2b292c5795f55553b6c790592309de97009de96252854c5abecc

Tx prefix hash: b350c99fae80c8dc2bb499a174e7e31217262247bebae981d14199d01e6902ef
Tx public key: 3f833998f623fabf6bdc74246b1b1f6b7370ceb8769e8f4df6612147b3b0a055
Timestamp: 1727089611 Timestamp [UCT]: 2024-09-23 11:06:51 Age [y:d:h:m:s]: 00:108:16:58:46
Block: 1116331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77726 RingCT/type: yes/0
Extra: 013f833998f623fabf6bdc74246b1b1f6b7370ceb8769e8f4df6612147b3b0a055021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ebb4bfdd860a302fce5cbf2809ed018761ea1c32e717ed3c058f99b629a294d 0.600000000000 1596774 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": 1116341, "vin": [ { "gen": { "height": 1116331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ebb4bfdd860a302fce5cbf2809ed018761ea1c32e717ed3c058f99b629a294d" } } ], "extra": [ 1, 63, 131, 57, 152, 246, 35, 250, 191, 107, 220, 116, 36, 107, 27, 31, 107, 115, 112, 206, 184, 118, 158, 143, 77, 246, 97, 33, 71, 179, 176, 160, 85, 2, 17, 0, 0, 0, 4, 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