Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bfd186a0ee98ab1f9a6acc72a552e5f34a4562c6acf606c182b069b40316044

Tx prefix hash: bc7f22054d3eba1ccd08a263792b72c11e35806900d06eeec23db46b486a1816
Tx public key: 4f43f7a12e9a3fa9f23e50e52ca13314be85906d57854520672a175c88dcb6ed
Timestamp: 1697245938 Timestamp [UCT]: 2023-10-14 01:12:18 Age [y:d:h:m:s]: 01:105:08:43:27
Block: 869115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336520 RingCT/type: yes/0
Extra: 014f43f7a12e9a3fa9f23e50e52ca13314be85906d57854520672a175c88dcb6ed021100000001faf35c9c000000000000000000

1 output(s) for total of 0.809582752000 dcy

stealth address amount amount idx
00: d1b44a945a343946202a562191ae4e0133107df1c2deebbab305e2cfff9625c2 0.809582752000 1323950 of 0

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": 869125, "vin": [ { "gen": { "height": 869115 } } ], "vout": [ { "amount": 809582752, "target": { "key": "d1b44a945a343946202a562191ae4e0133107df1c2deebbab305e2cfff9625c2" } } ], "extra": [ 1, 79, 67, 247, 161, 46, 154, 63, 169, 242, 62, 80, 229, 44, 161, 51, 20, 190, 133, 144, 109, 87, 133, 69, 32, 103, 42, 23, 92, 136, 220, 182, 237, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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