Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38a04691bb75b52e2da1b4e146a595f65b4fbc056a1f74368aa03afc0046ceee

Tx prefix hash: a32ec3a8b195a322ef7ca210cbd8b9f3501d933615a110bf525222b32ac42738
Tx public key: c2f13c35f5348b1e68e54cf8ae848fdb9e2de5156164e88d1f8d91898aeddc28
Timestamp: 1678136065 Timestamp [UCT]: 2023-03-06 20:54:25 Age [y:d:h:m:s]: 01:356:13:20:53
Block: 711385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515483 RingCT/type: yes/0
Extra: 01c2f13c35f5348b1e68e54cf8ae848fdb9e2de5156164e88d1f8d91898aeddc280211000000148b7b6602000000000000000000

1 output(s) for total of 2.697031890000 dcy

stealth address amount amount idx
00: bceff6e9d5234a5bf1ae0a282d4d9a3c0ce5b5edcbf649637f1c1b1d04c425c3 2.697031890000 1155512 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": 711395, "vin": [ { "gen": { "height": 711385 } } ], "vout": [ { "amount": 2697031890, "target": { "key": "bceff6e9d5234a5bf1ae0a282d4d9a3c0ce5b5edcbf649637f1c1b1d04c425c3" } } ], "extra": [ 1, 194, 241, 60, 53, 245, 52, 139, 30, 104, 229, 76, 248, 174, 132, 143, 219, 158, 45, 229, 21, 97, 100, 232, 141, 31, 141, 145, 137, 138, 237, 220, 40, 2, 17, 0, 0, 0, 20, 139, 123, 102, 2, 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