Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f0c4dad56c248c1c2f27691c2b2ae236fd3571614ea4939f269fbcd799cba5

Tx prefix hash: bf285c2592b32658e7eb807d9ebfec016658b6ae690a7769edaf6f63344b11b0
Tx public key: 7341db99904184a0eb4483b7fff7e9e42ba331695caf791fb186d6252646e57d
Timestamp: 1735862905 Timestamp [UCT]: 2025-01-03 00:08:25 Age [y:d:h:m:s]: 00:166:12:26:12
Block: 1188936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118721 RingCT/type: yes/0
Extra: 017341db99904184a0eb4483b7fff7e9e42ba331695caf791fb186d6252646e57d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d79fb1fefa294e9acc0b9c1b663b298bd387f2c0434d3bd0d8a91bbeae82c0b2 0.600000000000 1675441 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": 1188946, "vin": [ { "gen": { "height": 1188936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d79fb1fefa294e9acc0b9c1b663b298bd387f2c0434d3bd0d8a91bbeae82c0b2" } } ], "extra": [ 1, 115, 65, 219, 153, 144, 65, 132, 160, 235, 68, 131, 183, 255, 247, 233, 228, 43, 163, 49, 105, 92, 175, 121, 31, 177, 134, 214, 37, 38, 70, 229, 125, 2, 17, 0, 0, 0, 6, 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