Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa8b59e83b8fc2e25883ddb3e0d679f6c8c9e24b5ba60e059052781a74e37d5e

Tx prefix hash: 918b5b51ca93ee104d4d96a3b51d6e789280f4ede617d5131e5124d949373ef0
Tx public key: 7078361ecfe92e3bfe275b7425afd3c1d148e944727e04e46cac4e00c10a4847
Timestamp: 1731448358 Timestamp [UCT]: 2024-11-12 21:52:38 Age [y:d:h:m:s]: 00:144:23:52:22
Block: 1152374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103441 RingCT/type: yes/0
Extra: 017078361ecfe92e3bfe275b7425afd3c1d148e944727e04e46cac4e00c10a4847021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af4f39686ee74659f76a229f3873cb3fc4a1601a87ceb01cff4fbc61dc0b8542 0.600000000000 1637971 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": 1152384, "vin": [ { "gen": { "height": 1152374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af4f39686ee74659f76a229f3873cb3fc4a1601a87ceb01cff4fbc61dc0b8542" } } ], "extra": [ 1, 112, 120, 54, 30, 207, 233, 46, 59, 254, 39, 91, 116, 37, 175, 211, 193, 209, 72, 233, 68, 114, 126, 4, 228, 108, 172, 78, 0, 193, 10, 72, 71, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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