Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f3844223404cb56c16a3f5b45acc2d2d85617ff9692554a5bf0586f18d3a21

Tx prefix hash: 012bd5852add33320757d6d44e55221ea73fcb795c77c33113b86b0205119d7f
Tx public key: 155e43b4913fa6927d121f9febe7ed78e91a914ebe3107f8a42e600b6b09a0e9
Timestamp: 1699991187 Timestamp [UCT]: 2023-11-14 19:46:27 Age [y:d:h:m:s]: 01:067:17:22:19
Block: 891676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309756 RingCT/type: yes/0
Extra: 01155e43b4913fa6927d121f9febe7ed78e91a914ebe3107f8a42e600b6b09a0e902110000000433af99f4000000000000000000

1 output(s) for total of 0.681564961000 dcy

stealth address amount amount idx
00: 4b6137cd2fd5fb0e6abc8adc5454e1d520dc268cdd32994363661a272906f827 0.681564961000 1347727 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": 891686, "vin": [ { "gen": { "height": 891676 } } ], "vout": [ { "amount": 681564961, "target": { "key": "4b6137cd2fd5fb0e6abc8adc5454e1d520dc268cdd32994363661a272906f827" } } ], "extra": [ 1, 21, 94, 67, 180, 145, 63, 166, 146, 125, 18, 31, 159, 235, 231, 237, 120, 233, 26, 145, 78, 190, 49, 7, 248, 164, 46, 96, 11, 107, 9, 160, 233, 2, 17, 0, 0, 0, 4, 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