Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ac99f5385be0bc095ef75a2b367fb414b0a0e16d618caf74dae7aaa40a093bc

Tx prefix hash: cdba180857a53c1e175255e7df8f3290f4f311e267db1301751ec66ea66c3aaf
Tx public key: eeca39e851edfc477e8e18fc69a419ff8bb7394252e9a575ba04ac804b664733
Timestamp: 1718746852 Timestamp [UCT]: 2024-06-18 21:40:52 Age [y:d:h:m:s]: 01:133:06:01:03
Block: 1047170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353777 RingCT/type: yes/0
Extra: 01eeca39e851edfc477e8e18fc69a419ff8bb7394252e9a575ba04ac804b66473302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 585da6555b8e7a93190d8aaeba8e468eb30918e8b3d5dec1a4a32cc0c290ea67 0.600000000000 1516989 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": 1047180, "vin": [ { "gen": { "height": 1047170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "585da6555b8e7a93190d8aaeba8e468eb30918e8b3d5dec1a4a32cc0c290ea67" } } ], "extra": [ 1, 238, 202, 57, 232, 81, 237, 252, 71, 126, 142, 24, 252, 105, 164, 25, 255, 139, 183, 57, 66, 82, 233, 165, 117, 186, 4, 172, 128, 75, 102, 71, 51, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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