Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8565b0bc59c89a7c971c0f8519d3dff67e13e4729f8f84a0436d8042277a7727

Tx prefix hash: f2a2f69ee8415116c041825dba664d79b986bebb89d0d45bb42e13f05202ec16
Tx public key: e85b1ddf8427eb54a9445c8ca9713da77e90a6f1fb8e7dcbd3bd3643c61099ab
Timestamp: 1577191156 Timestamp [UCT]: 2019-12-24 12:39:16 Age [y:d:h:m:s]: 05:312:16:43:07
Block: 30697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371027 RingCT/type: yes/0
Extra: 01e85b1ddf8427eb54a9445c8ca9713da77e90a6f1fb8e7dcbd3bd3643c61099ab02110000010978873133000000000000000000

1 output(s) for total of 485.633223746000 dcy

stealth address amount amount idx
00: 0f5d9060d5b1074b5b117d7450d36d693fb75f884a4e83a1d336004871431788 485.633223746000 50683 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": 30707, "vin": [ { "gen": { "height": 30697 } } ], "vout": [ { "amount": 485633223746, "target": { "key": "0f5d9060d5b1074b5b117d7450d36d693fb75f884a4e83a1d336004871431788" } } ], "extra": [ 1, 232, 91, 29, 223, 132, 39, 235, 84, 169, 68, 92, 140, 169, 113, 61, 167, 126, 144, 166, 241, 251, 142, 125, 203, 211, 189, 54, 67, 198, 16, 153, 171, 2, 17, 0, 0, 1, 9, 120, 135, 49, 51, 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