Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7c1ebafe110cd7f33a01dc52b88b8acef1ce153a3c8e54b7a246a8659672a9

Tx prefix hash: d520c9b08d146086f7a7b6baf73b5dc8d036211a527aae4d8510849b3f4a4735
Tx public key: 8e49d18915e5d73663c6d98f77eb045c6313d8efb2588eef45b38df084daf471
Timestamp: 1575861039 Timestamp [UCT]: 2019-12-09 03:10:39 Age [y:d:h:m:s]: 05:155:23:28:05
Block: 23524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1257486 RingCT/type: yes/0
Extra: 018e49d18915e5d73663c6d98f77eb045c6313d8efb2588eef45b38df084daf4710211000000139159db1e000000000000000000

1 output(s) for total of 512.936480652000 dcy

stealth address amount amount idx
00: 9eb053b551f21ce98c37c60397c39ae22f78e114893aca34fb2490d2b2713b40 512.936480652000 37957 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": 23534, "vin": [ { "gen": { "height": 23524 } } ], "vout": [ { "amount": 512936480652, "target": { "key": "9eb053b551f21ce98c37c60397c39ae22f78e114893aca34fb2490d2b2713b40" } } ], "extra": [ 1, 142, 73, 209, 137, 21, 229, 215, 54, 99, 198, 217, 143, 119, 235, 4, 92, 99, 19, 216, 239, 178, 88, 142, 239, 69, 179, 141, 240, 132, 218, 244, 113, 2, 17, 0, 0, 0, 19, 145, 89, 219, 30, 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