Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee2c69b262ebb374f7f3cbfe843ad2aa2335f1d5e0604bc9e65a4fa1b401e27

Tx prefix hash: f6a18928c439a7cdd6b779857aece6d65a3d0e6995b3899a2369a6ff174b1b1e
Tx public key: 57978b56b5ded4d08d4d8d78a2ba989a5f67b2b09fc859d064a9bcf0101c9c43
Timestamp: 1578637508 Timestamp [UCT]: 2020-01-10 06:25:08 Age [y:d:h:m:s]: 05:331:20:52:03
Block: 42268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1385144 RingCT/type: yes/0
Extra: 0157978b56b5ded4d08d4d8d78a2ba989a5f67b2b09fc859d064a9bcf0101c9c430211000000a02264afe6000000000000000000

1 output(s) for total of 444.587140501000 dcy

stealth address amount amount idx
00: ce9b73c4232843e1584240509bffaa7116ee94b54a062a554f75ab3331615985 444.587140501000 76074 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": 42278, "vin": [ { "gen": { "height": 42268 } } ], "vout": [ { "amount": 444587140501, "target": { "key": "ce9b73c4232843e1584240509bffaa7116ee94b54a062a554f75ab3331615985" } } ], "extra": [ 1, 87, 151, 139, 86, 181, 222, 212, 208, 141, 77, 141, 120, 162, 186, 152, 154, 95, 103, 178, 176, 159, 200, 89, 208, 100, 169, 188, 240, 16, 28, 156, 67, 2, 17, 0, 0, 0, 160, 34, 100, 175, 230, 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