Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6005863772b0ca6a3aaac1a3a95cc9ade2d2faae31ab0141ad34d4356f05980

Tx prefix hash: 5f161d90d4f609201f22a8066f949c28638e8c56cc7dcc502a835ee5ce4d9bb5
Tx public key: 3834fab9acad2d2960a4999a3c0b45d83d2dcb6e364567d0736cc0012a840eb8
Timestamp: 1725243468 Timestamp [UCT]: 2024-09-02 02:17:48 Age [y:d:h:m:s]: 00:127:03:11:53
Block: 1101031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90928 RingCT/type: yes/0
Extra: 013834fab9acad2d2960a4999a3c0b45d83d2dcb6e364567d0736cc0012a840eb8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 139412dc9e74a705966acc435526726908f4fae07aecd4ec2a86ac65e1a22976 0.600000000000 1577012 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": 1101041, "vin": [ { "gen": { "height": 1101031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "139412dc9e74a705966acc435526726908f4fae07aecd4ec2a86ac65e1a22976" } } ], "extra": [ 1, 56, 52, 250, 185, 172, 173, 45, 41, 96, 164, 153, 154, 60, 11, 69, 216, 61, 45, 203, 110, 54, 69, 103, 208, 115, 108, 192, 1, 42, 132, 14, 184, 2, 17, 0, 0, 0, 3, 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