Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6cc11999592fcb8578216eb26c14362d9e3b44174ee8163f8050a204a0817ca

Tx prefix hash: 128b2eccf9fbad2b7a24810fe536b01e66b23eda2316259f70f6ab8a8fa8a4a2
Tx public key: e8c02950caf3d3844ea8a433641adb1ee05ba6c26f1e38fd63b8e14bbfd71cd5
Timestamp: 1714198996 Timestamp [UCT]: 2024-04-27 06:23:16 Age [y:d:h:m:s]: 00:257:16:28:47
Block: 1009453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184458 RingCT/type: yes/0
Extra: 01e8c02950caf3d3844ea8a433641adb1ee05ba6c26f1e38fd63b8e14bbfd71cd50211000000070011055b000000000000000000

1 output(s) for total of 0.615570000000 dcy

stealth address amount amount idx
00: 37718640e20ee7e0d5764ca8ed553d320074d320a487b579c45b0e6c781040b6 0.615570000000 1471127 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": 1009463, "vin": [ { "gen": { "height": 1009453 } } ], "vout": [ { "amount": 615570000, "target": { "key": "37718640e20ee7e0d5764ca8ed553d320074d320a487b579c45b0e6c781040b6" } } ], "extra": [ 1, 232, 192, 41, 80, 202, 243, 211, 132, 78, 168, 164, 51, 100, 26, 219, 30, 224, 91, 166, 194, 111, 30, 56, 253, 99, 184, 225, 75, 191, 215, 28, 213, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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