Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa65f95702cb0f053e014ed91a0ee1268ecc5db921e148e2f27398fe027b1ffd

Tx prefix hash: b3fff0d154c8b19006e6269f85e7016de3fe59d6402d07150fb88e5f27d6747b
Tx public key: f28582ec525d2c6314b38fb9ef5f8ed93ca54278e33e294440bf0cf3b65ae377
Timestamp: 1733486022 Timestamp [UCT]: 2024-12-06 11:53:42 Age [y:d:h:m:s]: 00:157:19:01:45
Block: 1169256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112596 RingCT/type: yes/0
Extra: 01f28582ec525d2c6314b38fb9ef5f8ed93ca54278e33e294440bf0cf3b65ae3770211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b795b6ab9e60742737c93ed4b0ea39fefc3668b92039bdbd7ab3af8d5ad2a977 0.600000000000 1654971 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": 1169266, "vin": [ { "gen": { "height": 1169256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b795b6ab9e60742737c93ed4b0ea39fefc3668b92039bdbd7ab3af8d5ad2a977" } } ], "extra": [ 1, 242, 133, 130, 236, 82, 93, 44, 99, 20, 179, 143, 185, 239, 95, 142, 217, 60, 165, 66, 120, 227, 62, 41, 68, 64, 191, 12, 243, 182, 90, 227, 119, 2, 17, 0, 0, 0, 4, 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