Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 756b7d5c74ff58bd5a9b77efda9ad9b177c2a3beeb6f40a871f3d1c0602b8064

Tx prefix hash: 00457efd36fbe96dc86805b440bc0bfae3f9e862e0a1ad7f057566e894056855
Tx public key: 7e1c07a0f2087497274d85efc2e654ca6868ebabe47d9170aa702d76080b2e0f
Timestamp: 1695708471 Timestamp [UCT]: 2023-09-26 06:07:51 Age [y:d:h:m:s]: 01:030:10:17:21
Block: 856368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283005 RingCT/type: yes/0
Extra: 017e1c07a0f2087497274d85efc2e654ca6868ebabe47d9170aa702d76080b2e0f02110000000233af99f4000000000000000000

1 output(s) for total of 0.892272212000 dcy

stealth address amount amount idx
00: fd66e98883d0c1d1943408bfa7010814c6509c4f5b39e808c99a28f4eb0f0a7c 0.892272212000 1310440 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": 856378, "vin": [ { "gen": { "height": 856368 } } ], "vout": [ { "amount": 892272212, "target": { "key": "fd66e98883d0c1d1943408bfa7010814c6509c4f5b39e808c99a28f4eb0f0a7c" } } ], "extra": [ 1, 126, 28, 7, 160, 242, 8, 116, 151, 39, 77, 133, 239, 194, 230, 84, 202, 104, 104, 235, 171, 228, 125, 145, 112, 170, 112, 45, 118, 8, 11, 46, 15, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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