Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e11115fdb43a84645904d08a3743e35ea7c0dd3018536cf2db377ae1f24a01a

Tx prefix hash: 852b566ade8402e8c5018bc9dbdc16ce6ada3121443d73a450510c87272371b9
Tx public key: b6bc1a9691ba686477c5a3e9fbccaca3c53ceac40435a1e5f021f3019a859b4b
Timestamp: 1731086609 Timestamp [UCT]: 2024-11-08 17:23:29 Age [y:d:h:m:s]: 01:009:11:48:55
Block: 1149384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265204 RingCT/type: yes/0
Extra: 01b6bc1a9691ba686477c5a3e9fbccaca3c53ceac40435a1e5f021f3019a859b4b0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdb00555a5febe515faea626ec6124b6d946d644277d8c1a3d45459e51e9f277 0.600000000000 1634451 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": 1149394, "vin": [ { "gen": { "height": 1149384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdb00555a5febe515faea626ec6124b6d946d644277d8c1a3d45459e51e9f277" } } ], "extra": [ 1, 182, 188, 26, 150, 145, 186, 104, 100, 119, 197, 163, 233, 251, 204, 172, 163, 197, 60, 234, 196, 4, 53, 161, 229, 240, 33, 243, 1, 154, 133, 155, 75, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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