Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca3d8982f22ded3526ed472f0d6cb85b17d5b31546e507834ae430b8b4e9a06

Tx prefix hash: 5c2c33b01543fc8363c0692368d63e20bb5c3cd5d57b56050229976a944b771c
Tx public key: 46542ce00b02357e265cdd6b4294f0f2bb073df10235edf9e83d449b9aad4dcf
Timestamp: 1723276301 Timestamp [UCT]: 2024-08-10 07:51:41 Age [y:d:h:m:s]: 01:084:01:24:23
Block: 1084724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318533 RingCT/type: yes/0
Extra: 0146542ce00b02357e265cdd6b4294f0f2bb073df10235edf9e83d449b9aad4dcf021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058e13f7ab5b14ce3e0e896c3df49a5ee689f43ccb445d1181809cccc1df2e1a 0.600000000000 1559103 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": 1084734, "vin": [ { "gen": { "height": 1084724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058e13f7ab5b14ce3e0e896c3df49a5ee689f43ccb445d1181809cccc1df2e1a" } } ], "extra": [ 1, 70, 84, 44, 224, 11, 2, 53, 126, 38, 92, 221, 107, 66, 148, 240, 242, 187, 7, 61, 241, 2, 53, 237, 249, 232, 61, 68, 155, 154, 173, 77, 207, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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