Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f3c09e728c1ea6c8331da184c745a884fff819441e549809b4fbfd01c3bb65

Tx prefix hash: 363152cc439fdca81b1f219753b892e163d768c3df5ff355bd5bd0624ff06bee
Tx public key: 7f75ae0de28bc05b8e8a6b8246fa27ca5a1e257dd9c97104192f34b77a253fdc
Timestamp: 1632156749 Timestamp [UCT]: 2021-09-20 16:52:29 Age [y:d:h:m:s]: 03:049:10:23:14
Block: 337650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 811310 RingCT/type: yes/0
Extra: 017f75ae0de28bc05b8e8a6b8246fa27ca5a1e257dd9c97104192f34b77a253fdc0211000000b18d0de867000000000000000000

1 output(s) for total of 46.691019261000 dcy

stealth address amount amount idx
00: fb5c369877cec3b31d2b3e664cbaf460760c143e0f8211524c91e3a0fe7e8c36 46.691019261000 695189 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": 337660, "vin": [ { "gen": { "height": 337650 } } ], "vout": [ { "amount": 46691019261, "target": { "key": "fb5c369877cec3b31d2b3e664cbaf460760c143e0f8211524c91e3a0fe7e8c36" } } ], "extra": [ 1, 127, 117, 174, 13, 226, 139, 192, 91, 142, 138, 107, 130, 70, 250, 39, 202, 90, 30, 37, 125, 217, 201, 113, 4, 25, 47, 52, 183, 122, 37, 63, 220, 2, 17, 0, 0, 0, 177, 141, 13, 232, 103, 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