Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7b0a2d05326dca69ca3be86b466d475082a898e0887fde9db59cf0a11ba5ab8

Tx prefix hash: f873da2a717ad6fcc8ca0388d3eea9b5fc95f98668efa734cff95a4df34c8c32
Tx public key: 9e92e81615c0e1e5ff2f2e3616c416df939fd9c985572991f9b09e13876c1e32
Timestamp: 1710521160 Timestamp [UCT]: 2024-03-15 16:46:00 Age [y:d:h:m:s]: 01:236:05:30:39
Block: 978984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427521 RingCT/type: yes/0
Extra: 019e92e81615c0e1e5ff2f2e3616c416df939fd9c985572991f9b09e13876c1e320211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f798ff9b0ca7d9586eb533570ddc8a9bed2d08ab684bf1b8cbd4d1d3131038d3 0.600000000000 1439013 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": 978994, "vin": [ { "gen": { "height": 978984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f798ff9b0ca7d9586eb533570ddc8a9bed2d08ab684bf1b8cbd4d1d3131038d3" } } ], "extra": [ 1, 158, 146, 232, 22, 21, 192, 225, 229, 255, 47, 46, 54, 22, 196, 22, 223, 147, 159, 217, 201, 133, 87, 41, 145, 249, 176, 158, 19, 135, 108, 30, 50, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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