Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea63fe2bc7fa83657b34e68a3031bd88834022c4998193012ac50e37f1ff0ae

Tx prefix hash: eb923da31fab082c376d089fab0e7876ccdb3f76ec6cb82ac2f22eb174620d6f
Tx public key: 7a841d7796f0c2ce8563675ed9af8a7ca6c74e9acdd9072266767e1a3ba531fe
Timestamp: 1724885021 Timestamp [UCT]: 2024-08-28 22:43:41 Age [y:d:h:m:s]: 00:055:11:41:57
Block: 1098051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39718 RingCT/type: yes/0
Extra: 017a841d7796f0c2ce8563675ed9af8a7ca6c74e9acdd9072266767e1a3ba531fe02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0e69e9648bcfc423cee5ee89d5b2916db0b4a3b6148094eb3bf06c0c92337bb 0.600000000000 1573634 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": 1098061, "vin": [ { "gen": { "height": 1098051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0e69e9648bcfc423cee5ee89d5b2916db0b4a3b6148094eb3bf06c0c92337bb" } } ], "extra": [ 1, 122, 132, 29, 119, 150, 240, 194, 206, 133, 99, 103, 94, 217, 175, 138, 124, 166, 199, 78, 154, 205, 217, 7, 34, 102, 118, 126, 26, 59, 165, 49, 254, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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