Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18d22b4c21aa4ca8cecbe380907a514fd5bdf34cce85b3b27337ad57a7e330ca

Tx prefix hash: 58cd0b773ce3246a026532fc7d78b828626cf1f243eb8f611d7e0a7afb2546af
Tx public key: 77617d707a420a448685b0dcc85a5b4db7420e75ed433cfb1e5ba8c7c695f636
Timestamp: 1584922736 Timestamp [UCT]: 2020-03-23 00:18:56 Age [y:d:h:m:s]: 04:239:18:14:56
Block: 86928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068202 RingCT/type: yes/0
Extra: 0177617d707a420a448685b0dcc85a5b4db7420e75ed433cfb1e5ba8c7c695f636021100000094c2c2f844000000000000000000

1 output(s) for total of 316.207546373000 dcy

stealth address amount amount idx
00: 89a7f7026d38da8181326dfa338cb3ef3a29a6ce0ec7fad90085b59c4a9167ac 316.207546373000 156772 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": 86938, "vin": [ { "gen": { "height": 86928 } } ], "vout": [ { "amount": 316207546373, "target": { "key": "89a7f7026d38da8181326dfa338cb3ef3a29a6ce0ec7fad90085b59c4a9167ac" } } ], "extra": [ 1, 119, 97, 125, 112, 122, 66, 10, 68, 134, 133, 176, 220, 200, 90, 91, 77, 183, 66, 14, 117, 237, 67, 60, 251, 30, 91, 168, 199, 198, 149, 246, 54, 2, 17, 0, 0, 0, 148, 194, 194, 248, 68, 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