Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b2ac0c89813e88b4d534b3d5d8ab47235fe7ed32d5f0f50f0832793e24d5db5

Tx prefix hash: 295248639a8c9c31e6f1f9e6347c6185e778f0743058982d6fff78f182247f05
Tx public key: d9d5ba0794f92d3d667ce9eed0f83a7faddcda3924487f7862d2bb16759ba822
Timestamp: 1720392640 Timestamp [UCT]: 2024-07-07 22:50:40 Age [y:d:h:m:s]: 00:289:21:36:24
Block: 1060809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207140 RingCT/type: yes/0
Extra: 01d9d5ba0794f92d3d667ce9eed0f83a7faddcda3924487f7862d2bb16759ba822021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db8d3ccaf2df7cbe0466c8db3501103104e1738cfa7df597c5a6ac18af46a65 0.600000000000 1531296 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": 1060819, "vin": [ { "gen": { "height": 1060809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db8d3ccaf2df7cbe0466c8db3501103104e1738cfa7df597c5a6ac18af46a65" } } ], "extra": [ 1, 217, 213, 186, 7, 148, 249, 45, 61, 102, 124, 233, 238, 208, 248, 58, 127, 173, 220, 218, 57, 36, 72, 127, 120, 98, 210, 187, 22, 117, 155, 168, 34, 2, 17, 0, 0, 0, 8, 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