Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab496583c337307e303ba75154863383ade44efa08cd1a19da7ca12f1c7cd343

Tx prefix hash: fe336c895b62b06f51fcf8c17c544f43296c52865f71f24ba4573457e89d1c68
Tx public key: aa124275c5b75722d80576781994bcd72ae9c011089b2a3f77d6e36be4be55cb
Timestamp: 1731224523 Timestamp [UCT]: 2024-11-10 07:42:03 Age [y:d:h:m:s]: 00:169:06:46:37
Block: 1150521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120841 RingCT/type: yes/0
Extra: 01aa124275c5b75722d80576781994bcd72ae9c011089b2a3f77d6e36be4be55cb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a8b7ce058dc1e419070b3aa0ba96d70b21be6d85e58e09e30b14c2d0b56ae7 0.600000000000 1635860 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": 1150531, "vin": [ { "gen": { "height": 1150521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a8b7ce058dc1e419070b3aa0ba96d70b21be6d85e58e09e30b14c2d0b56ae7" } } ], "extra": [ 1, 170, 18, 66, 117, 197, 183, 87, 34, 216, 5, 118, 120, 25, 148, 188, 215, 42, 233, 192, 17, 8, 155, 42, 63, 119, 214, 227, 107, 228, 190, 85, 203, 2, 17, 0, 0, 0, 3, 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