Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 598c1fa53cf0e444e3251eae8eab978622efc1e35246ab5ffbb0658c980f8154

Tx prefix hash: 61d97e6c27ca3de98175e9744b4ae950c46e9d8d745a4667543327e2ca4d127e
Tx public key: fd78183e908dbbc6baf72bb5bccfa535c395b8cbae661ebfacfec1e2e85794b0
Timestamp: 1578484974 Timestamp [UCT]: 2020-01-08 12:02:54 Age [y:d:h:m:s]: 04:326:21:55:47
Block: 41208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122987 RingCT/type: yes/0
Extra: 01fd78183e908dbbc6baf72bb5bccfa535c395b8cbae661ebfacfec1e2e85794b00211000000018a2ee0d9000000000000000000

1 output(s) for total of 448.204106413000 dcy

stealth address amount amount idx
00: 9ed07ff134a4468dfec43320ef8e8627c96926af1aa6cf0f48f4ab29e9e1d2a7 448.204106413000 73169 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": 41218, "vin": [ { "gen": { "height": 41208 } } ], "vout": [ { "amount": 448204106413, "target": { "key": "9ed07ff134a4468dfec43320ef8e8627c96926af1aa6cf0f48f4ab29e9e1d2a7" } } ], "extra": [ 1, 253, 120, 24, 62, 144, 141, 187, 198, 186, 247, 43, 181, 188, 207, 165, 53, 195, 149, 184, 203, 174, 102, 30, 191, 172, 254, 193, 226, 232, 87, 148, 176, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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