Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b058be4e2750602aefb0bcc656a08aff93ddf2fbdf43a339fbed9a15a205298

Tx prefix hash: 3091ebd8c96f29dbf746dbd70736ba040984bcbc0e7081e3d52239a1a1ef54c4
Tx public key: 102c4d26c9db51f29f956c72c24c7be999d5593328c64964b946b1206d4f92aa
Timestamp: 1582435309 Timestamp [UCT]: 2020-02-23 05:21:49 Age [y:d:h:m:s]: 05:101:04:40:17
Block: 70636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1225629 RingCT/type: yes/0
Extra: 01102c4d26c9db51f29f956c72c24c7be999d5593328c64964b946b1206d4f92aa021100000001724f989b000000000000000000

1 output(s) for total of 358.058849891000 dcy

stealth address amount amount idx
00: 8921528cee22a1cdb4de9612d073a288e97bdce547f807c6e2071d4ab3f507ed 358.058849891000 130516 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": 70646, "vin": [ { "gen": { "height": 70636 } } ], "vout": [ { "amount": 358058849891, "target": { "key": "8921528cee22a1cdb4de9612d073a288e97bdce547f807c6e2071d4ab3f507ed" } } ], "extra": [ 1, 16, 44, 77, 38, 201, 219, 81, 242, 159, 149, 108, 114, 194, 76, 123, 233, 153, 213, 89, 51, 40, 198, 73, 100, 185, 70, 177, 32, 109, 79, 146, 170, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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