Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad84c8c72f6ed9f675df4efcbedddb37c93ab3bb48988d921d0e507e9da5f736

Tx prefix hash: e8a6501aae7d1b55efac590e36d1d782f033b492d2e5b6804daab3bcf53f81b9
Tx public key: 309db4bf5a32e80154b0da1e78331f664e7cc0e6080392597f291d8b3fbf1bbc
Timestamp: 1703187112 Timestamp [UCT]: 2023-12-21 19:31:52 Age [y:d:h:m:s]: 01:144:13:23:49
Block: 918166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364471 RingCT/type: yes/0
Extra: 01309db4bf5a32e80154b0da1e78331f664e7cc0e6080392597f291d8b3fbf1bbc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a6b267b52a7dcdfe83e041988558206cba6658264a4d00be35f509bf309b036 0.600000000000 1375808 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": 918176, "vin": [ { "gen": { "height": 918166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a6b267b52a7dcdfe83e041988558206cba6658264a4d00be35f509bf309b036" } } ], "extra": [ 1, 48, 157, 180, 191, 90, 50, 232, 1, 84, 176, 218, 30, 120, 51, 31, 102, 78, 124, 192, 230, 8, 3, 146, 89, 127, 41, 29, 139, 63, 191, 27, 188, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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