Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa6a51fd67f8329e8e188f1db3beffa2094a6b0f5806a58136894bd4cbc92cd

Tx prefix hash: cdad1ba70d697925c0621c93606d32ecae53a392ec1f408ef350ab0a8ee23ebb
Tx public key: 0fbe0a6ee74e1f64b899f6ad2f2affebea815abdf08e6a2cd19b0528ff413b1b
Timestamp: 1577161968 Timestamp [UCT]: 2019-12-24 04:32:48 Age [y:d:h:m:s]: 05:006:20:21:49
Block: 30353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155021 RingCT/type: yes/0
Extra: 010fbe0a6ee74e1f64b899f6ad2f2affebea815abdf08e6a2cd19b0528ff413b1b02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 486.887665602000 dcy

stealth address amount amount idx
00: 671448014715250d38925be1a0f3105b16448661ee12114472e0a486294cd4d9 486.887665602000 50117 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": 30363, "vin": [ { "gen": { "height": 30353 } } ], "vout": [ { "amount": 486887665602, "target": { "key": "671448014715250d38925be1a0f3105b16448661ee12114472e0a486294cd4d9" } } ], "extra": [ 1, 15, 190, 10, 110, 231, 78, 31, 100, 184, 153, 246, 173, 47, 42, 255, 235, 234, 129, 90, 189, 240, 142, 106, 44, 209, 155, 5, 40, 255, 65, 59, 27, 2, 17, 0, 0, 0, 10, 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