Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cbef015ef757634a70d1702c4ab9a7a227b3b9809b247288734ea05f5c44e9d

Tx prefix hash: f8070868c0e06aa7586ee0410619a5c41ca4b7ff84fb6fb179734da8b0048313
Tx public key: 3a1623edbdebc5e732f3f7fb2600177a7ab9fcb616e7ed3328d7747bb7864ee0
Timestamp: 1728659494 Timestamp [UCT]: 2024-10-11 15:11:34 Age [y:d:h:m:s]: 00:155:16:23:39
Block: 1129348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111059 RingCT/type: yes/0
Extra: 013a1623edbdebc5e732f3f7fb2600177a7ab9fcb616e7ed3328d7747bb7864ee0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04f3c26e72556559ee06dfdbff69ffb7d7eddd776d3a936cbfb4173839a43a32 0.600000000000 1612173 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": 1129358, "vin": [ { "gen": { "height": 1129348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04f3c26e72556559ee06dfdbff69ffb7d7eddd776d3a936cbfb4173839a43a32" } } ], "extra": [ 1, 58, 22, 35, 237, 189, 235, 197, 231, 50, 243, 247, 251, 38, 0, 23, 122, 122, 185, 252, 182, 22, 231, 237, 51, 40, 215, 116, 123, 183, 134, 78, 224, 2, 17, 0, 0, 0, 6, 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