Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bda084ff4ad72ce3d86623fe537058ca08d7bd6553ae2fbbf82a22106e75026

Tx prefix hash: 397ca937d6e88fe12c8e6749585c0360581ca1e0d69592e4061ba55aa1254409
Tx public key: cc7e9606a3019f2c119a265623ea9cd3cda46f71dd6f0230328f763ea3e89101
Timestamp: 1583346898 Timestamp [UCT]: 2020-03-04 18:34:58 Age [y:d:h:m:s]: 04:297:09:49:56
Block: 76457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106895 RingCT/type: yes/0
Extra: 01cc7e9606a3019f2c119a265623ea9cd3cda46f71dd6f0230328f763ea3e8910102110000003cc71d3ff9000000000000000000

1 output(s) for total of 342.505078454000 dcy

stealth address amount amount idx
00: ea4e5ea5d0ca88372016cf3a09b4d992ac57bc97247d01fb721040616a1445ba 342.505078454000 140716 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": 76467, "vin": [ { "gen": { "height": 76457 } } ], "vout": [ { "amount": 342505078454, "target": { "key": "ea4e5ea5d0ca88372016cf3a09b4d992ac57bc97247d01fb721040616a1445ba" } } ], "extra": [ 1, 204, 126, 150, 6, 163, 1, 159, 44, 17, 154, 38, 86, 35, 234, 156, 211, 205, 164, 111, 113, 221, 111, 2, 48, 50, 143, 118, 62, 163, 232, 145, 1, 2, 17, 0, 0, 0, 60, 199, 29, 63, 249, 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