Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561609c0d3e596463e854f14161e57746ae74b1c21db306608d55e9da1538e1d

Tx prefix hash: 0f785967255c81872111cbedfc8c2e76b13decc46c3467592523cb2e008462d1
Tx public key: 57aa80dab59161f7b2325fa8cc4cde5f4e5206ff17247b0eb8e4a6d9155ae8dd
Timestamp: 1704982386 Timestamp [UCT]: 2024-01-11 14:13:06 Age [y:d:h:m:s]: 01:079:20:03:23
Block: 933043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318151 RingCT/type: yes/0
Extra: 0157aa80dab59161f7b2325fa8cc4cde5f4e5206ff17247b0eb8e4a6d9155ae8dd02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f003b1e7caba214bba0b614b79b4d58b8609d23bfa5e112f3f9d7093137915dc 0.600000000000 1390991 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": 933053, "vin": [ { "gen": { "height": 933043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f003b1e7caba214bba0b614b79b4d58b8609d23bfa5e112f3f9d7093137915dc" } } ], "extra": [ 1, 87, 170, 128, 218, 181, 145, 97, 247, 178, 50, 95, 168, 204, 76, 222, 95, 78, 82, 6, 255, 23, 36, 123, 14, 184, 228, 166, 217, 21, 90, 232, 221, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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