Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfc0a15ee7076a5e18f4016656e17a63f02eac826b3462d7936b2304226e752

Tx prefix hash: 8df5c1db76c841dba840ebcc18a28bc9d952969bbfffa4d71163fa9910588d73
Tx public key: 050f9c2b64035d88dc70f0a3eb38e94059feccbe4e3047fab3ede8eb25e7a02a
Timestamp: 1667422340 Timestamp [UCT]: 2022-11-02 20:52:20 Age [y:d:h:m:s]: 02:178:14:55:15
Block: 622649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649353 RingCT/type: yes/0
Extra: 01050f9c2b64035d88dc70f0a3eb38e94059feccbe4e3047fab3ede8eb25e7a02a02110000000233af99f4000000000000000000

1 output(s) for total of 5.307688364000 dcy

stealth address amount amount idx
00: 0cb733a502785558af0adfba954e17ff21a3a0c2ac98c71243c130cfd7afe559 5.307688364000 1060738 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": 622659, "vin": [ { "gen": { "height": 622649 } } ], "vout": [ { "amount": 5307688364, "target": { "key": "0cb733a502785558af0adfba954e17ff21a3a0c2ac98c71243c130cfd7afe559" } } ], "extra": [ 1, 5, 15, 156, 43, 100, 3, 93, 136, 220, 112, 240, 163, 235, 56, 233, 64, 89, 254, 204, 190, 78, 48, 71, 250, 179, 237, 232, 235, 37, 231, 160, 42, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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