Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342304b55e04c522911792fd34c1d78469e226b562cc00d57cf4889f4604af8a

Tx prefix hash: 94d68278b19865875c44dfa46c9b68a59dd4437fa0b9c92bd6fc59e155dceb7f
Tx public key: 4b4924dee7fd0986eb8e07e7235ac95b8feeed38c9c0adba82d1f22ac6ff6aff
Timestamp: 1717251451 Timestamp [UCT]: 2024-06-01 14:17:31 Age [y:d:h:m:s]: 00:306:06:10:55
Block: 1034775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218865 RingCT/type: yes/0
Extra: 014b4924dee7fd0986eb8e07e7235ac95b8feeed38c9c0adba82d1f22ac6ff6aff02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d948a758e7abf3a274b511ccbb98292fcd6101f2bda87bdb0fde2021e5c4eea5 0.600000000000 1503294 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": 1034785, "vin": [ { "gen": { "height": 1034775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d948a758e7abf3a274b511ccbb98292fcd6101f2bda87bdb0fde2021e5c4eea5" } } ], "extra": [ 1, 75, 73, 36, 222, 231, 253, 9, 134, 235, 142, 7, 231, 35, 90, 201, 91, 143, 238, 237, 56, 201, 192, 173, 186, 130, 209, 242, 42, 198, 255, 106, 255, 2, 17, 0, 0, 0, 1, 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