Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fa131c4d5db6773f6025ed74be90a7f6e979d4f21a8391136f46211ac7d67d5

Tx prefix hash: 96c69ca7064bbb235c00c537adb9d25b99a46867eb5075f8c69e0222e9613d82
Tx public key: 766e0509eda54199e0dc4c590741d53df15abcb6a9f4e60d8f5653b44ec0af2a
Timestamp: 1745819954 Timestamp [UCT]: 2025-04-28 05:59:14 Age [y:d:h:m:s]: 00:014:18:54:22
Block: 1271111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10560 RingCT/type: yes/0
Extra: 01766e0509eda54199e0dc4c590741d53df15abcb6a9f4e60d8f5653b44ec0af2a0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e0f593aa230802ea01e1349d45c0a5c204298409111607994263f6df98f963 0.600000000000 1758360 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": 1271121, "vin": [ { "gen": { "height": 1271111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e0f593aa230802ea01e1349d45c0a5c204298409111607994263f6df98f963" } } ], "extra": [ 1, 118, 110, 5, 9, 237, 165, 65, 153, 224, 220, 76, 89, 7, 65, 213, 61, 241, 90, 188, 182, 169, 244, 230, 13, 143, 86, 83, 180, 78, 192, 175, 42, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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