Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a43ce074e02c3b309e74f4419e3ed82c2feda6e748b918c9a95247ac91bfe61

Tx prefix hash: 1c5e26debb026c2af2f43b30fbc9707bd9923ff7045adf3796ad775121fe348f
Tx public key: cbec3a5d69d49ae68ffdd6f2acb585984544fae9d2b4b659d2322b3c851813f2
Timestamp: 1698556144 Timestamp [UCT]: 2023-10-29 05:09:04 Age [y:d:h:m:s]: 01:152:13:27:56
Block: 879987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370031 RingCT/type: yes/0
Extra: 01cbec3a5d69d49ae68ffdd6f2acb585984544fae9d2b4b659d2322b3c851813f202110000000633af99f4000000000000000000

1 output(s) for total of 0.745139836000 dcy

stealth address amount amount idx
00: 9d7316836426894520bda6d449bdfd7501a313804896b251791a40680df010af 0.745139836000 1335529 of 0

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": 879997, "vin": [ { "gen": { "height": 879987 } } ], "vout": [ { "amount": 745139836, "target": { "key": "9d7316836426894520bda6d449bdfd7501a313804896b251791a40680df010af" } } ], "extra": [ 1, 203, 236, 58, 93, 105, 212, 154, 230, 143, 253, 214, 242, 172, 181, 133, 152, 69, 68, 250, 233, 210, 180, 182, 89, 210, 50, 43, 60, 133, 24, 19, 242, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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