Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b369ed9c367011ae912f8617d5b4d45164bf89b00416abdef44324dfe49338a

Tx prefix hash: d7c7d7bcba935571bce3b53771a2bef88980f30b4f07ac5a6d2709bf12133ff7
Tx public key: 977e4d636d40f66df1ac7b7f04e6910671bd493b4fc6d46c26555c18120ea0c5
Timestamp: 1712364716 Timestamp [UCT]: 2024-04-06 00:51:56 Age [y:d:h:m:s]: 01:052:15:44:45
Block: 994222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298659 RingCT/type: yes/0
Extra: 01977e4d636d40f66df1ac7b7f04e6910671bd493b4fc6d46c26555c18120ea0c502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45bc91455bf9aae496c26a0128f56ff8b32c5fec83843a04d4fc6b8cbde8162b 0.600000000000 1454624 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": 994232, "vin": [ { "gen": { "height": 994222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45bc91455bf9aae496c26a0128f56ff8b32c5fec83843a04d4fc6b8cbde8162b" } } ], "extra": [ 1, 151, 126, 77, 99, 109, 64, 246, 109, 241, 172, 123, 127, 4, 230, 145, 6, 113, 189, 73, 59, 79, 198, 212, 108, 38, 85, 92, 24, 18, 14, 160, 197, 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