Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d4584185ad12b00160a5e8f920e5c8722344cc9f729222c73579640ccbcc3e

Tx prefix hash: f7d6d1baafeb355156a7220979728c79198c6835f2ed575598e29caca21ade2c
Tx public key: fb343bad8554b4538b017f7616769e8eea19108a30e59d6f5d71c54a95bca44d
Timestamp: 1683375826 Timestamp [UCT]: 2023-05-06 12:23:46 Age [y:d:h:m:s]: 02:025:23:17:43
Block: 754179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540706 RingCT/type: yes/0
Extra: 01fb343bad8554b4538b017f7616769e8eea19108a30e59d6f5d71c54a95bca44d021100000002faf35c9c000000000000000000

1 output(s) for total of 1.945772654000 dcy

stealth address amount amount idx
00: 7d3b9c00e7cb593e6e2a664cfa52ad69ff1d1e7e33be0bf0497cd8087eee36dc 1.945772654000 1202432 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": 754189, "vin": [ { "gen": { "height": 754179 } } ], "vout": [ { "amount": 1945772654, "target": { "key": "7d3b9c00e7cb593e6e2a664cfa52ad69ff1d1e7e33be0bf0497cd8087eee36dc" } } ], "extra": [ 1, 251, 52, 59, 173, 133, 84, 180, 83, 139, 1, 127, 118, 22, 118, 158, 142, 234, 25, 16, 138, 48, 229, 157, 111, 93, 113, 197, 74, 149, 188, 164, 77, 2, 17, 0, 0, 0, 2, 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