Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4663be0712b2ff6bfddc0711d1218836dc790fd5e3e8f4ea65a18d9b0733fac

Tx prefix hash: 5a32367e9bc83090dec39f4cd47dddc42ca7c11e37df77531a8f3e4310a6b9e1
Tx public key: ce68bff22eae3f28c837414cdb1e02e6e9c64f6fd3c57d191d6159034525a813
Timestamp: 1660360428 Timestamp [UCT]: 2022-08-13 03:13:48 Age [y:d:h:m:s]: 02:236:18:32:51
Block: 564665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690446 RingCT/type: yes/0
Extra: 01ce68bff22eae3f28c837414cdb1e02e6e9c64f6fd3c57d191d6159034525a81302110000000275e3f0e9000000000000000000

1 output(s) for total of 8.260960816000 dcy

stealth address amount amount idx
00: f5987c0f566b76616255453c3705da17346f1db4f8dfdcf4df02c4b3d18fac89 8.260960816000 997519 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": 564675, "vin": [ { "gen": { "height": 564665 } } ], "vout": [ { "amount": 8260960816, "target": { "key": "f5987c0f566b76616255453c3705da17346f1db4f8dfdcf4df02c4b3d18fac89" } } ], "extra": [ 1, 206, 104, 191, 242, 46, 174, 63, 40, 200, 55, 65, 76, 219, 30, 2, 230, 233, 198, 79, 111, 211, 197, 125, 25, 29, 97, 89, 3, 69, 37, 168, 19, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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