Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8cfb4a13e8efc77d73a8da4c85f7b160c1ab4b5c4dee56d5f52f26d7f00c24f

Tx prefix hash: 462b0c17176e63aae8bb12e37abe68bccc55388c265e1ed0c803387dc0262d5e
Tx public key: a848a2d3fc2cfa3ca78ab485bdb76747e9ee3bc300bad6098d99fb06d1ca44d8
Timestamp: 1729621338 Timestamp [UCT]: 2024-10-22 18:22:18 Age [y:d:h:m:s]: 00:033:00:10:56
Block: 1137285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23580 RingCT/type: yes/0
Extra: 01a848a2d3fc2cfa3ca78ab485bdb76747e9ee3bc300bad6098d99fb06d1ca44d8021100000001aa787773000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0faa766238be84057a53e1bf25a611580a4a8b3a52280cf73e83f6dd2c95b5be 0.600000000000 1620746 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": 1137295, "vin": [ { "gen": { "height": 1137285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0faa766238be84057a53e1bf25a611580a4a8b3a52280cf73e83f6dd2c95b5be" } } ], "extra": [ 1, 168, 72, 162, 211, 252, 44, 250, 60, 167, 138, 180, 133, 189, 183, 103, 71, 233, 238, 59, 195, 0, 186, 214, 9, 141, 153, 251, 6, 209, 202, 68, 216, 2, 17, 0, 0, 0, 1, 170, 120, 119, 115, 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