Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06cf7b2c58537db0a1449d0936ed5b79cc5d0d0e3dead8a5861b2b74b547a2fd

Tx prefix hash: fefa306d86232751607ca2b891b3264856a9b9efcdf8a6db21e79d0112465615
Tx public key: 827b73df7d2162cfbe3b021f3b19b5a7096581899282380aa8aea388dbd89fb7
Timestamp: 1721774449 Timestamp [UCT]: 2024-07-23 22:40:49 Age [y:d:h:m:s]: 00:256:00:37:31
Block: 1072261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182898 RingCT/type: yes/0
Extra: 01827b73df7d2162cfbe3b021f3b19b5a7096581899282380aa8aea388dbd89fb702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 977f2b81fc5cf36b33dc18c909de4cb8e22ceb2380c7c23779e778db32258695 0.600000000000 1544720 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": 1072271, "vin": [ { "gen": { "height": 1072261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "977f2b81fc5cf36b33dc18c909de4cb8e22ceb2380c7c23779e778db32258695" } } ], "extra": [ 1, 130, 123, 115, 223, 125, 33, 98, 207, 190, 59, 2, 31, 59, 25, 181, 167, 9, 101, 129, 137, 146, 130, 56, 10, 168, 174, 163, 136, 219, 216, 159, 183, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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