Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a44c8b0d24d903e2761b78fb4e431fd177b3a4a80748fa953f9d63e295dc8f1

Tx prefix hash: 03d6976d0a894b9230a562334789c1497f79015b12c14c30896f635b084a5f34
Tx public key: 1fadd5259247dbe75f780419990df528096fc0243efe35e4ed81bd3f00c26971
Timestamp: 1731475935 Timestamp [UCT]: 2024-11-13 05:32:15 Age [y:d:h:m:s]: 00:141:16:30:23
Block: 1152600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101077 RingCT/type: yes/0
Extra: 011fadd5259247dbe75f780419990df528096fc0243efe35e4ed81bd3f00c2697102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41f7683f5938695945769e825ff660a0f0c87925e486e5c0e0961f2d3dd3ac18 0.600000000000 1638201 of 15

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": 1152610, "vin": [ { "gen": { "height": 1152600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41f7683f5938695945769e825ff660a0f0c87925e486e5c0e0961f2d3dd3ac18" } } ], "extra": [ 1, 31, 173, 213, 37, 146, 71, 219, 231, 95, 120, 4, 25, 153, 13, 245, 40, 9, 111, 192, 36, 62, 254, 53, 228, 237, 129, 189, 63, 0, 194, 105, 113, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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