Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67d21f77d1bd0484f1a6664ac5ed724bb4fc20bbdc2aac35e05d3973f4e54fa

Tx prefix hash: 8776176ca3397c52afa39f716e8509e167e256f893040eb30057b3d0ddf1b5be
Tx public key: 0c234e742d711dcb2496b8a2c1abdac0102648610031ccbfd1d0451a730ae405
Timestamp: 1731541261 Timestamp [UCT]: 2024-11-13 23:41:01 Age [y:d:h:m:s]: 00:192:10:53:05
Block: 1153147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137413 RingCT/type: yes/0
Extra: 010c234e742d711dcb2496b8a2c1abdac0102648610031ccbfd1d0451a730ae405021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01fe442a684d54cd0061d7f31709f5a92cd0a3d81e6cdf4db30d1e6676d54d24 0.600000000000 1638754 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": 1153157, "vin": [ { "gen": { "height": 1153147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01fe442a684d54cd0061d7f31709f5a92cd0a3d81e6cdf4db30d1e6676d54d24" } } ], "extra": [ 1, 12, 35, 78, 116, 45, 113, 29, 203, 36, 150, 184, 162, 193, 171, 218, 192, 16, 38, 72, 97, 0, 49, 204, 191, 209, 208, 69, 26, 115, 10, 228, 5, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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