Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4de77a8134b96e237b9f958750b1ff6e21da5d6fa7c81cb3f4dacb41ab5f40b

Tx prefix hash: b42d453f8e893e778ff28bc22cab1a0a41dcc25cb85186a8c126eb7cac64b274
Tx public key: f81bb79507e11df09bac74d109f5437bf8b34fcf6d301a4f1ede711e41c98ba9
Timestamp: 1731148373 Timestamp [UCT]: 2024-11-09 10:32:53 Age [y:d:h:m:s]: 00:147:08:03:04
Block: 1149898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105125 RingCT/type: yes/0
Extra: 01f81bb79507e11df09bac74d109f5437bf8b34fcf6d301a4f1ede711e41c98ba90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa6d46be4018bbc86715daebc45017a144a9d69b5b79208612cc87cf6f5996f4 0.600000000000 1635073 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": 1149908, "vin": [ { "gen": { "height": 1149898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa6d46be4018bbc86715daebc45017a144a9d69b5b79208612cc87cf6f5996f4" } } ], "extra": [ 1, 248, 27, 183, 149, 7, 225, 29, 240, 155, 172, 116, 209, 9, 245, 67, 123, 248, 179, 79, 207, 109, 48, 26, 79, 30, 222, 113, 30, 65, 201, 139, 169, 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