Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2e07e4e7ba25f18bc360251d5cca91f0db3df60d005fe669015202988c04b1d

Tx prefix hash: e59164666bf923861fa0fcd3a367961be048f880c235656c2d5a5c282dad7ef9
Tx public key: 806f45af76a614f34f3e558581f0ca7ebf6e26a8b94144e70b3f2cb361f8ee05
Timestamp: 1707862285 Timestamp [UCT]: 2024-02-13 22:11:25 Age [y:d:h:m:s]: 01:276:06:15:31
Block: 956930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456209 RingCT/type: yes/0
Extra: 01806f45af76a614f34f3e558581f0ca7ebf6e26a8b94144e70b3f2cb361f8ee050211000000026d0f39ce000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dad4831cdc76028555c6e282580a0b24309de8f714764a300bb7adc7924aa466 0.600000000000 1416242 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": 956940, "vin": [ { "gen": { "height": 956930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dad4831cdc76028555c6e282580a0b24309de8f714764a300bb7adc7924aa466" } } ], "extra": [ 1, 128, 111, 69, 175, 118, 166, 20, 243, 79, 62, 85, 133, 129, 240, 202, 126, 191, 110, 38, 168, 185, 65, 68, 231, 11, 63, 44, 179, 97, 248, 238, 5, 2, 17, 0, 0, 0, 2, 109, 15, 57, 206, 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