Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bb64f70fe4a67221e11894e722c4adbc29ad9cf0e8b4140704bc10764fd2091

Tx prefix hash: aa67e232f8a807b67b8cd1f5fe4d4e9e809f0db867600d400e75af1116b4f5c9
Tx public key: b127384edaa651d0a29c8d24b56f3e77d13b0ec964a4b3c1e5df517a7c9ac414
Timestamp: 1710459641 Timestamp [UCT]: 2024-03-14 23:40:41 Age [y:d:h:m:s]: 01:061:01:58:07
Block: 978481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304649 RingCT/type: yes/0
Extra: 01b127384edaa651d0a29c8d24b56f3e77d13b0ec964a4b3c1e5df517a7c9ac4140211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a2fa51a42cb06f0f1992ce94dd38c64fa325593f2b2bae80e8e52801e1e9067 0.600000000000 1438508 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": 978491, "vin": [ { "gen": { "height": 978481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a2fa51a42cb06f0f1992ce94dd38c64fa325593f2b2bae80e8e52801e1e9067" } } ], "extra": [ 1, 177, 39, 56, 78, 218, 166, 81, 208, 162, 156, 141, 36, 181, 111, 62, 119, 209, 59, 14, 201, 100, 164, 179, 193, 229, 223, 81, 122, 124, 154, 196, 20, 2, 17, 0, 0, 0, 1, 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