Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e93134dcdf21cf06e2b10c4ac3aba12bf70408a7824bb1e5d2176130145d86

Tx prefix hash: 0fd492d624ccd7c971a05e6f37fc2032be2978f4d79ab1750066c84270ce80aa
Tx public key: 3bcb542b0a0ee7e4ea7f9d49ed04b05ddbda7275da8a8c19a36a8f65f8d406a5
Timestamp: 1577101947 Timestamp [UCT]: 2019-12-23 11:52:27 Age [y:d:h:m:s]: 05:010:22:03:39
Block: 29951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157839 RingCT/type: yes/0
Extra: 013bcb542b0a0ee7e4ea7f9d49ed04b05ddbda7275da8a8c19a36a8f65f8d406a5021100000014d81c26c0000000000000000000

1 output(s) for total of 488.383256189000 dcy

stealth address amount amount idx
00: fbfb2a7ea4a1e7b36fe306afc47b125cf2b3e67d130c5ca9d4877441a0eba49d 488.383256189000 49427 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": 29961, "vin": [ { "gen": { "height": 29951 } } ], "vout": [ { "amount": 488383256189, "target": { "key": "fbfb2a7ea4a1e7b36fe306afc47b125cf2b3e67d130c5ca9d4877441a0eba49d" } } ], "extra": [ 1, 59, 203, 84, 43, 10, 14, 231, 228, 234, 127, 157, 73, 237, 4, 176, 93, 219, 218, 114, 117, 218, 138, 140, 25, 163, 106, 143, 101, 248, 212, 6, 165, 2, 17, 0, 0, 0, 20, 216, 28, 38, 192, 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