Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb82a8ae4369bb842f5df3c3c12fa578a2214569fdd3a8c29f7b07df75c4600

Tx prefix hash: 2cfb845a3eff7303a656bf9a7bc72afd2e53ffa829a934e7eca30d4ff2786d7a
Tx public key: 3d174027e5a9f3086214c24545ee5e3736505c9f449a40ed54d40b3bec09bcba
Timestamp: 1626679255 Timestamp [UCT]: 2021-07-19 07:20:55 Age [y:d:h:m:s]: 03:299:23:39:37
Block: 296774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985806 RingCT/type: yes/0
Extra: 013d174027e5a9f3086214c24545ee5e3736505c9f449a40ed54d40b3bec09bcba0211000000072a81b072000000000000000000

1 output(s) for total of 63.777139483000 dcy

stealth address amount amount idx
00: 17708d9aba257d49e5dcfa38fd9360e9089a3472bbff7b11ee3475323f76041c 63.777139483000 621234 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": 296784, "vin": [ { "gen": { "height": 296774 } } ], "vout": [ { "amount": 63777139483, "target": { "key": "17708d9aba257d49e5dcfa38fd9360e9089a3472bbff7b11ee3475323f76041c" } } ], "extra": [ 1, 61, 23, 64, 39, 229, 169, 243, 8, 98, 20, 194, 69, 69, 238, 94, 55, 54, 80, 92, 159, 68, 154, 64, 237, 84, 212, 11, 59, 236, 9, 188, 186, 2, 17, 0, 0, 0, 7, 42, 129, 176, 114, 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