Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a106f4a0b1b9ad8e92fe721810691c0a308d4281a8547d6a2a90eba35ec0508

Tx prefix hash: 96f5d5ed0bc7d10eef9a01ce21050574feeee3c950c597e386c6cfa2cbc8b364
Tx public key: 8439a8f56b830f641d3c1f97e960be052ee4370e4bdfcf4bb2603a2e187479a1
Timestamp: 1718581534 Timestamp [UCT]: 2024-06-16 23:45:34 Age [y:d:h:m:s]: 01:168:03:06:11
Block: 1045811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378733 RingCT/type: yes/0
Extra: 018439a8f56b830f641d3c1f97e960be052ee4370e4bdfcf4bb2603a2e187479a102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b957d52d4b9d3118ffb9b44dfa44bfed3eed35ca0028ef4d22314dbc9c38fa96 0.600000000000 1515492 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": 1045821, "vin": [ { "gen": { "height": 1045811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b957d52d4b9d3118ffb9b44dfa44bfed3eed35ca0028ef4d22314dbc9c38fa96" } } ], "extra": [ 1, 132, 57, 168, 245, 107, 131, 15, 100, 29, 60, 31, 151, 233, 96, 190, 5, 46, 228, 55, 14, 75, 223, 207, 75, 178, 96, 58, 46, 24, 116, 121, 161, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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