Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b8c0427f8c4ba72e2e86ac5647de77b981963a969db8eeea613b23bb20c22ba

Tx prefix hash: 19ee5519ef33d6d3aa1f8eb3ca2260ab2aa30340ca4d4e890dae9229d5b863c0
Tx public key: 2a258ac69878a7359de39582e19cbf71c27b855e26e8fc23c6d4249d4d86a2f5
Timestamp: 1738333515 Timestamp [UCT]: 2025-01-31 14:25:15 Age [y:d:h:m:s]: 00:339:05:51:50
Block: 1209126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240300 RingCT/type: yes/0
Extra: 012a258ac69878a7359de39582e19cbf71c27b855e26e8fc23c6d4249d4d86a2f5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 614fd08a0c46ffdb033f965be1b185977b8437e969d0726e1b35a3b8689bb55a 0.600000000000 1695867 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": 1209136, "vin": [ { "gen": { "height": 1209126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "614fd08a0c46ffdb033f965be1b185977b8437e969d0726e1b35a3b8689bb55a" } } ], "extra": [ 1, 42, 37, 138, 198, 152, 120, 167, 53, 157, 227, 149, 130, 225, 156, 191, 113, 194, 123, 133, 94, 38, 232, 252, 35, 198, 212, 36, 157, 77, 134, 162, 245, 2, 17, 0, 0, 0, 4, 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