Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc41d76da21e9e6b74c9e5f3d983b7b75a4c51d3d0516896cca3b98630420ce6

Tx prefix hash: f81b826a6c7a0af408d15bffdcd6d338bd529c5ff796ad94970bb8bf0582bf98
Tx public key: 90115be27fefd40502945896ab0abd88cfe349aa9d42bacf0326ad17f1ab910f
Timestamp: 1735354979 Timestamp [UCT]: 2024-12-28 03:02:59 Age [y:d:h:m:s]: 00:311:04:31:12
Block: 1184726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219913 RingCT/type: yes/0
Extra: 0190115be27fefd40502945896ab0abd88cfe349aa9d42bacf0326ad17f1ab910f0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf0f535c91f611d8bffc2a386f21effc641370b343bf55bf48ec00e60e1fbff6 0.600000000000 1671185 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": 1184736, "vin": [ { "gen": { "height": 1184726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf0f535c91f611d8bffc2a386f21effc641370b343bf55bf48ec00e60e1fbff6" } } ], "extra": [ 1, 144, 17, 91, 226, 127, 239, 212, 5, 2, 148, 88, 150, 171, 10, 189, 136, 207, 227, 73, 170, 157, 66, 186, 207, 3, 38, 173, 23, 241, 171, 145, 15, 2, 17, 0, 0, 0, 6, 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