Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11da449b85a5b35dcb23beb0084c7ae802a1064e8a3377ccceb5adc6b1ea164c

Tx prefix hash: 71ef59801079a7ffd8b507a0415d09e92f3863ec0f5cc9679e8249f7b83191fa
Tx public key: 6a05e41c70ccd3ce02e0262139bec98811ea9be2b7f6fa8ce51959fcac58811f
Timestamp: 1675019704 Timestamp [UCT]: 2023-01-29 19:15:04 Age [y:d:h:m:s]: 01:309:13:58:48
Block: 685532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482212 RingCT/type: yes/0
Extra: 016a05e41c70ccd3ce02e0262139bec98811ea9be2b7f6fa8ce51959fcac58811f02110000000e835e4d22000000000000000000

1 output(s) for total of 3.285094299000 dcy

stealth address amount amount idx
00: 7fbe916e58d90271d89bde836ea944031a9ee5998d0fb2f125f3b944cefea191 3.285094299000 1127869 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": 685542, "vin": [ { "gen": { "height": 685532 } } ], "vout": [ { "amount": 3285094299, "target": { "key": "7fbe916e58d90271d89bde836ea944031a9ee5998d0fb2f125f3b944cefea191" } } ], "extra": [ 1, 106, 5, 228, 28, 112, 204, 211, 206, 2, 224, 38, 33, 57, 190, 201, 136, 17, 234, 155, 226, 183, 246, 250, 140, 229, 25, 89, 252, 172, 88, 129, 31, 2, 17, 0, 0, 0, 14, 131, 94, 77, 34, 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