Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1a8c5571f08d1afe299312481a53e77178ec44f5f62967bc84dc7dbc7b61b61

Tx prefix hash: a5bd19df6225892f760c8f7f04d30066dee63e73beb589510a9ebfad73fa6f7b
Tx public key: 45a620554622d3a773638bc1b0a2a34c99ee10b35ac30d086c3b72f7f61d1414
Timestamp: 1695391621 Timestamp [UCT]: 2023-09-22 14:07:01 Age [y:d:h:m:s]: 01:101:12:30:49
Block: 853737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333834 RingCT/type: yes/0
Extra: 0145a620554622d3a773638bc1b0a2a34c99ee10b35ac30d086c3b72f7f61d1414021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.910363773000 dcy

stealth address amount amount idx
00: 5d75e398a708f81f3e2fd58ce58c7c225ac1df5546d7d296b9f8978ca420d5e9 0.910363773000 1307669 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": 853747, "vin": [ { "gen": { "height": 853737 } } ], "vout": [ { "amount": 910363773, "target": { "key": "5d75e398a708f81f3e2fd58ce58c7c225ac1df5546d7d296b9f8978ca420d5e9" } } ], "extra": [ 1, 69, 166, 32, 85, 70, 34, 211, 167, 115, 99, 139, 193, 176, 162, 163, 76, 153, 238, 16, 179, 90, 195, 13, 8, 108, 59, 114, 247, 246, 29, 20, 20, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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