Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a0ac85c3064b6b557e5135289e6f7f03e76e9134164d8fe0a38dd6c85b148e

Tx prefix hash: 41b12c34b4c3493081a73ee6e3da83dbef44b8c0645f46c255a8b8bc6b280d9b
Tx public key: c4eda989d03ab230e3eecfa7bfd65b2720f60eb5cec685d03d80ab451aa3ae12
Timestamp: 1734350391 Timestamp [UCT]: 2024-12-16 11:59:51 Age [y:d:h:m:s]: 00:185:16:39:26
Block: 1176438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132392 RingCT/type: yes/0
Extra: 01c4eda989d03ab230e3eecfa7bfd65b2720f60eb5cec685d03d80ab451aa3ae120211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a85d5604221351c7fe6b40af97571a3ea0d34aa56fed3a44870e1f5b9c021390 0.600000000000 1662771 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": 1176448, "vin": [ { "gen": { "height": 1176438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a85d5604221351c7fe6b40af97571a3ea0d34aa56fed3a44870e1f5b9c021390" } } ], "extra": [ 1, 196, 237, 169, 137, 208, 58, 178, 48, 227, 238, 207, 167, 191, 214, 91, 39, 32, 246, 14, 181, 206, 198, 133, 208, 61, 128, 171, 69, 26, 163, 174, 18, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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