Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b90dd5266eb87c32f8d4e7eb9678779b77cc848096329f1319efc963b5d1ec91

Tx prefix hash: ee43b6d9874047c037d661697c173acb85246ab3fb77e4bebcfe919dfc1d402b
Tx public key: 785d258f4a781808184840b125dd1fde2e4cb549c350aa3b1dfc21724507e6e2
Timestamp: 1702239644 Timestamp [UCT]: 2023-12-10 20:20:44 Age [y:d:h:m:s]: 01:120:22:19:07
Block: 910315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347564 RingCT/type: yes/0
Extra: 01785d258f4a781808184840b125dd1fde2e4cb549c350aa3b1dfc21724507e6e202110000000be6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f353193cdbf35ceefcd21f1880abf79d2e6cad3860f6e6553b274070c87a3dc 0.600000000000 1367464 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": 910325, "vin": [ { "gen": { "height": 910315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f353193cdbf35ceefcd21f1880abf79d2e6cad3860f6e6553b274070c87a3dc" } } ], "extra": [ 1, 120, 93, 37, 143, 74, 120, 24, 8, 24, 72, 64, 177, 37, 221, 31, 222, 46, 76, 181, 73, 195, 80, 170, 59, 29, 252, 33, 114, 69, 7, 230, 226, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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