Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50b591325b948c5336e98c3ae2f699c1fd3b442970672c77b113b97e84c4c78

Tx prefix hash: 9c5c3d1e0ad8e8ec8fd9d40ec3fbfb142805c498ea4f591de1da826201a2aeb0
Tx public key: a8469534edb44661c7979bcd704c36dd95ecf65214f95906937eaba44c514d21
Timestamp: 1729096186 Timestamp [UCT]: 2024-10-16 16:29:46 Age [y:d:h:m:s]: 01:028:17:05:45
Block: 1132972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278889 RingCT/type: yes/0
Extra: 01a8469534edb44661c7979bcd704c36dd95ecf65214f95906937eaba44c514d21021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f4d6ab92bceced0d29999232dc988e4bc3f8b3cf145c33e89a85aac6e5a0c5 0.600000000000 1616025 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": 1132982, "vin": [ { "gen": { "height": 1132972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f4d6ab92bceced0d29999232dc988e4bc3f8b3cf145c33e89a85aac6e5a0c5" } } ], "extra": [ 1, 168, 70, 149, 52, 237, 180, 70, 97, 199, 151, 155, 205, 112, 76, 54, 221, 149, 236, 246, 82, 20, 249, 89, 6, 147, 126, 171, 164, 76, 81, 77, 33, 2, 17, 0, 0, 0, 3, 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