Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be19f173d9ec140d921e02a99129bae8c50bcd18007d8748050b2f96d09b079

Tx prefix hash: d1569cf9f6ec985608efbf57450eaa794caa22ec570ea1530e41e80505b4de20
Tx public key: fc7c97c146510eea71e55b59427b94f89c810d11c5a1d398d776f00778b036e0
Timestamp: 1730239957 Timestamp [UCT]: 2024-10-29 22:12:37 Age [y:d:h:m:s]: 00:195:08:35:40
Block: 1142380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139468 RingCT/type: yes/0
Extra: 01fc7c97c146510eea71e55b59427b94f89c810d11c5a1d398d776f00778b036e00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cb05e17bea0e4c00b74951ca371eaa2cb75c56d4cae0504f51419b16a4c1b45 0.600000000000 1626233 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": 1142390, "vin": [ { "gen": { "height": 1142380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cb05e17bea0e4c00b74951ca371eaa2cb75c56d4cae0504f51419b16a4c1b45" } } ], "extra": [ 1, 252, 124, 151, 193, 70, 81, 14, 234, 113, 229, 91, 89, 66, 123, 148, 248, 156, 129, 13, 17, 197, 161, 211, 152, 215, 118, 240, 7, 120, 176, 54, 224, 2, 17, 0, 0, 0, 2, 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