Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 591cb150f1f5c14abd0f58c2df3b836e6704012dba2e47b95b55f521390b3d71

Tx prefix hash: 03f2a8b581ba1aa367e8b2ef98a3cd5d54aee41ea664a41f1e1804e60c97742f
Tx public key: f1a41835bd74db8e4029d3f9ed24aecfaba30a251f910f5699d6a73f4c94c765
Timestamp: 1672950201 Timestamp [UCT]: 2023-01-05 20:23:21 Age [y:d:h:m:s]: 01:331:18:12:30
Block: 668361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498109 RingCT/type: yes/0
Extra: 01f1a41835bd74db8e4029d3f9ed24aecfaba30a251f910f5699d6a73f4c94c76502110000000733af99f4000000000000000000

1 output(s) for total of 3.744919760000 dcy

stealth address amount amount idx
00: e99a4e2b354be7b086597f3b35acbc895c4c457f90108b8bedad9e902a694c75 3.744919760000 1109606 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": 668371, "vin": [ { "gen": { "height": 668361 } } ], "vout": [ { "amount": 3744919760, "target": { "key": "e99a4e2b354be7b086597f3b35acbc895c4c457f90108b8bedad9e902a694c75" } } ], "extra": [ 1, 241, 164, 24, 53, 189, 116, 219, 142, 64, 41, 211, 249, 237, 36, 174, 207, 171, 163, 10, 37, 31, 145, 15, 86, 153, 214, 167, 63, 76, 148, 199, 101, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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