Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17cac5fdf31b5d933210b4b40743a14376aff11052711f48f4fd31a9ff4c9708

Tx prefix hash: 39f5a8d6e7b81e9c3b88d152fa67b24436ccd8f114a5f041411caef596365bba
Tx public key: 799a096075b01a230bc8b12e93a0cea71514f478d2aedba278052ca42baf33fb
Timestamp: 1677063009 Timestamp [UCT]: 2023-02-22 10:50:09 Age [y:d:h:m:s]: 01:284:03:40:59
Block: 702466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464003 RingCT/type: yes/0
Extra: 01799a096075b01a230bc8b12e93a0cea71514f478d2aedba278052ca42baf33fb021100000004835e4d22000000000000000000

1 output(s) for total of 2.886944562000 dcy

stealth address amount amount idx
00: add79cd9282ec74e5becd1e42d84940459515d7e13cb4e713ea1b20c8b8d96d7 2.886944562000 1145981 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": 702476, "vin": [ { "gen": { "height": 702466 } } ], "vout": [ { "amount": 2886944562, "target": { "key": "add79cd9282ec74e5becd1e42d84940459515d7e13cb4e713ea1b20c8b8d96d7" } } ], "extra": [ 1, 121, 154, 9, 96, 117, 176, 26, 35, 11, 200, 177, 46, 147, 160, 206, 167, 21, 20, 244, 120, 210, 174, 219, 162, 120, 5, 44, 164, 43, 175, 51, 251, 2, 17, 0, 0, 0, 4, 131, 94, 77, 34, 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