Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f576c912878be2545769cf08ba2151af1b9189316f9db79b9e7d9b1586dadb9

Tx prefix hash: 74039fa25c4e20285654ed70159bd77319963a3bb29816300d3daafff174b82d
Tx public key: 174149b24c9fe0c0af2411bc31b8a82a749eb3ef0fc3ba3d7b9bfc9cc0e94e7a
Timestamp: 1701689949 Timestamp [UCT]: 2023-12-04 11:39:09 Age [y:d:h:m:s]: 01:162:00:54:18
Block: 905749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377000 RingCT/type: yes/0
Extra: 01174149b24c9fe0c0af2411bc31b8a82a749eb3ef0fc3ba3d7b9bfc9cc0e94e7a021100000003faf35c9c000000000000000000

1 output(s) for total of 0.612177754000 dcy

stealth address amount amount idx
00: de57c92272309ea93d9c7084684effad53db7c3ce3d2cce172d4a1687ee25dc7 0.612177754000 1362664 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": 905759, "vin": [ { "gen": { "height": 905749 } } ], "vout": [ { "amount": 612177754, "target": { "key": "de57c92272309ea93d9c7084684effad53db7c3ce3d2cce172d4a1687ee25dc7" } } ], "extra": [ 1, 23, 65, 73, 178, 76, 159, 224, 192, 175, 36, 17, 188, 49, 184, 168, 42, 116, 158, 179, 239, 15, 195, 186, 61, 123, 155, 252, 156, 192, 233, 78, 122, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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