Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eea0ee513e236c7e119180f9f8190d8924bc99db266d0b7b0a6c206b9f58807f

Tx prefix hash: 53a5a252b14905659c6da3e32ed6c095ca9dac16489c9de8e987018f64f4d1d5
Tx public key: f8234256ee4844ff81028b55fa5be1dcd7a4741935e766fc846cd6a7ac640718
Timestamp: 1728905252 Timestamp [UCT]: 2024-10-14 11:27:32 Age [y:d:h:m:s]: 00:104:18:33:52
Block: 1131392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74646 RingCT/type: yes/0
Extra: 01f8234256ee4844ff81028b55fa5be1dcd7a4741935e766fc846cd6a7ac640718021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc267be2938b25aa041abebac228d54e3d9df86d02e8e09d0a74961c4e9a277a 0.600000000000 1614291 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": 1131402, "vin": [ { "gen": { "height": 1131392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc267be2938b25aa041abebac228d54e3d9df86d02e8e09d0a74961c4e9a277a" } } ], "extra": [ 1, 248, 35, 66, 86, 238, 72, 68, 255, 129, 2, 139, 85, 250, 91, 225, 220, 215, 164, 116, 25, 53, 231, 102, 252, 132, 108, 214, 167, 172, 100, 7, 24, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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