Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7687da7acd557a729a5a23e9b809cb58d99c9265e6e69b3cfd75f30181ae7883

Tx prefix hash: 23ff4fa54da489e74c50a819706b16a85f1c67cc2f899eec1c34dcf28bad5ace
Tx public key: bf384c085dc0a7413f6f3a05a96d1f8ef141d7f6ea35af82b33de8244ec6698c
Timestamp: 1725314268 Timestamp [UCT]: 2024-09-02 21:57:48 Age [y:d:h:m:s]: 00:228:10:50:21
Block: 1101615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163132 RingCT/type: yes/0
Extra: 01bf384c085dc0a7413f6f3a05a96d1f8ef141d7f6ea35af82b33de8244ec6698c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab80b33a25acabe7d707efdbafe0cbb65ef38c2f474b0380c1acad546ee334bb 0.600000000000 1577734 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": 1101625, "vin": [ { "gen": { "height": 1101615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab80b33a25acabe7d707efdbafe0cbb65ef38c2f474b0380c1acad546ee334bb" } } ], "extra": [ 1, 191, 56, 76, 8, 93, 192, 167, 65, 63, 111, 58, 5, 169, 109, 31, 142, 241, 65, 215, 246, 234, 53, 175, 130, 179, 61, 232, 36, 78, 198, 105, 140, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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