Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1a96805aaad910e09295c0c0f8015f6fc6b7180cbe3f060b3749774db12f52

Tx prefix hash: 8c1faf88ba4fed6819358995910f07c228422ccd72aa9c5cf191a02201ff32a9
Tx public key: 3211bd4ce9ebf19f9632728615556b7069cd4e7dfeeb36edeaccb59ef54e692c
Timestamp: 1721922570 Timestamp [UCT]: 2024-07-25 15:49:30 Age [y:d:h:m:s]: 00:307:23:34:03
Block: 1073492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220070 RingCT/type: yes/0
Extra: 013211bd4ce9ebf19f9632728615556b7069cd4e7dfeeb36edeaccb59ef54e692c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2053c53531c9b5c7b194a7c06724c5f8fc9551632d0b929c0d2f563347bfb4f5 0.600000000000 1545995 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": 1073502, "vin": [ { "gen": { "height": 1073492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2053c53531c9b5c7b194a7c06724c5f8fc9551632d0b929c0d2f563347bfb4f5" } } ], "extra": [ 1, 50, 17, 189, 76, 233, 235, 241, 159, 150, 50, 114, 134, 21, 85, 107, 112, 105, 205, 78, 125, 254, 235, 54, 237, 234, 204, 181, 158, 245, 78, 105, 44, 2, 17, 0, 0, 0, 4, 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