Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b79552d1f365a3297b7c1147d91a27dfc656e5d488a92dabc0b595f42bf0bba

Tx prefix hash: 821291210cfa4ef53bcde6b174a0c035cac9fce0c85b14386cdabda8159bf2b9
Tx public key: e74f60e99ee9df013babe5c09e85a8ab826102f16097728975c6ef9fdf8d11b2
Timestamp: 1730564851 Timestamp [UCT]: 2024-11-02 16:27:31 Age [y:d:h:m:s]: 01:006:13:15:58
Block: 1145056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263105 RingCT/type: yes/0
Extra: 01e74f60e99ee9df013babe5c09e85a8ab826102f16097728975c6ef9fdf8d11b20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bd1c9c9c5ab68b648c4793695edb70b9ec9c01d47c0ff6485722fad02000f6e 0.600000000000 1629421 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": 1145066, "vin": [ { "gen": { "height": 1145056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bd1c9c9c5ab68b648c4793695edb70b9ec9c01d47c0ff6485722fad02000f6e" } } ], "extra": [ 1, 231, 79, 96, 233, 158, 233, 223, 1, 59, 171, 229, 192, 158, 133, 168, 171, 130, 97, 2, 241, 96, 151, 114, 137, 117, 198, 239, 159, 223, 141, 17, 178, 2, 17, 0, 0, 0, 2, 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