Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65729a9f45fa4f43a3ecf3af6d1959f89ef4ee28c75dd49afa7b716c748928e3

Tx prefix hash: f9b29f886d5ef37ee7d197e1ffdab11a336c92a781b02b3d6d7ece7f8b4c0c81
Tx public key: 9d0b49d37310ba62b0a15aa947da89a03d4aa2c5251b75f8d3a398f1bf5a0625
Timestamp: 1580480240 Timestamp [UCT]: 2020-01-31 14:17:20 Age [y:d:h:m:s]: 04:328:15:22:15
Block: 55806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126150 RingCT/type: yes/0
Extra: 019d0b49d37310ba62b0a15aa947da89a03d4aa2c5251b75f8d3a398f1bf5a0625021100000002391a8d0e000000000000000000

1 output(s) for total of 400.951996463000 dcy

stealth address amount amount idx
00: fe6e686a073e51441a81fdd70985ba9d2f11e1034834a78bc227746584d7231c 400.951996463000 102969 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": 55816, "vin": [ { "gen": { "height": 55806 } } ], "vout": [ { "amount": 400951996463, "target": { "key": "fe6e686a073e51441a81fdd70985ba9d2f11e1034834a78bc227746584d7231c" } } ], "extra": [ 1, 157, 11, 73, 211, 115, 16, 186, 98, 176, 161, 90, 169, 71, 218, 137, 160, 61, 74, 162, 197, 37, 27, 117, 248, 211, 163, 152, 241, 191, 90, 6, 37, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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