Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36edc468172281d12efe7036a568761e38a5273f3e7f658d440b347b91350a12

Tx prefix hash: a4e8b3ea4b180772a794f2cbb9b9e2448cc84c5e0ce1aa480d3a2fd3fde7612f
Tx public key: 2a89287df67f813ecc409f14338d9001f3129518f56e4d3d8c22bc73a5a39903
Timestamp: 1643298696 Timestamp [UCT]: 2022-01-27 15:51:36 Age [y:d:h:m:s]: 03:090:21:27:17
Block: 426441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 844166 RingCT/type: yes/0
Extra: 012a89287df67f813ecc409f14338d9001f3129518f56e4d3d8c22bc73a5a39903021100000003db0c7f64000000000000000000

1 output(s) for total of 23.715061553000 dcy

stealth address amount amount idx
00: ee6115f7fdfb01c8752ab3ad5d001a73cd323dee71d5c8bb46f2a02d67972936 23.715061553000 835270 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": 426451, "vin": [ { "gen": { "height": 426441 } } ], "vout": [ { "amount": 23715061553, "target": { "key": "ee6115f7fdfb01c8752ab3ad5d001a73cd323dee71d5c8bb46f2a02d67972936" } } ], "extra": [ 1, 42, 137, 40, 125, 246, 127, 129, 62, 204, 64, 159, 20, 51, 141, 144, 1, 243, 18, 149, 24, 245, 110, 77, 61, 140, 34, 188, 115, 165, 163, 153, 3, 2, 17, 0, 0, 0, 3, 219, 12, 127, 100, 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