Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1d1b1818bd76ba1fac4dbdfeff2400de8d3bdb26ca0f9e088c17b470d358a5

Tx prefix hash: 387a7672a6f1b2c31678e5422d52554e11b92b0bc5e1b90ffde104f4ddea8d3d
Tx public key: fc5991465d1343ca17b18213b60fc43ec132fc804cc8a64018a4f0f97ad50aae
Timestamp: 1574491975 Timestamp [UCT]: 2019-11-23 06:52:55 Age [y:d:h:m:s]: 05:010:16:12:39
Block: 15171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1150846 RingCT/type: yes/0
Extra: 01fc5991465d1343ca17b18213b60fc43ec132fc804cc8a64018a4f0f97ad50aae021100000019d50ca400000000000000000000

1 output(s) for total of 546.679845644000 dcy

stealth address amount amount idx
00: b18e9007de98774bec694317a4c41b3fb7a9ba0771bdde1650b7a32db33118a3 546.679845644000 20093 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": 15181, "vin": [ { "gen": { "height": 15171 } } ], "vout": [ { "amount": 546679845644, "target": { "key": "b18e9007de98774bec694317a4c41b3fb7a9ba0771bdde1650b7a32db33118a3" } } ], "extra": [ 1, 252, 89, 145, 70, 93, 19, 67, 202, 23, 177, 130, 19, 182, 15, 196, 62, 193, 50, 252, 128, 76, 200, 166, 64, 24, 164, 240, 249, 122, 213, 10, 174, 2, 17, 0, 0, 0, 25, 213, 12, 164, 0, 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