Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea61e680dfaf1c8b00b0eb79ab64ff1b17a34c23f66b166991861f249a4d7664

Tx prefix hash: 6e6907927272656c2adfc3f791b871ce60c511d2ed7eab4b1d732b1dd071c925
Tx public key: b51b0b1cef364dac1f668f9e6b594b25418ee1e542cb47c6ee7d08ed1aa0b1bb
Timestamp: 1737289744 Timestamp [UCT]: 2025-01-19 12:29:04 Age [y:d:h:m:s]: 00:338:00:20:53
Block: 1200711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239155 RingCT/type: yes/0
Extra: 01b51b0b1cef364dac1f668f9e6b594b25418ee1e542cb47c6ee7d08ed1aa0b1bb02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94363512ae7d65b1612e7d3472302cb4b1ed2bfce49bdd5d17717c80e670c05c 0.600000000000 1687356 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": 1200721, "vin": [ { "gen": { "height": 1200711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94363512ae7d65b1612e7d3472302cb4b1ed2bfce49bdd5d17717c80e670c05c" } } ], "extra": [ 1, 181, 27, 11, 28, 239, 54, 77, 172, 31, 102, 143, 158, 107, 89, 75, 37, 65, 142, 225, 229, 66, 203, 71, 198, 238, 125, 8, 237, 26, 160, 177, 187, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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