Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1bcfd6e47b150b1bd843fa352633fd5ddb503501513de7adc2aa160c3d54ff1

Tx prefix hash: d2c7158e6fbf4a6102fdd2f3bb1a96056ed947db510c2dcd1b262aea0cba2bd4
Tx public key: d6f7df8c9738d1152c37788de9cca3330cb2254008aee98cff66837754dfdb29
Timestamp: 1719887480 Timestamp [UCT]: 2024-07-02 02:31:20 Age [y:d:h:m:s]: 00:289:11:49:17
Block: 1056619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206852 RingCT/type: yes/0
Extra: 01d6f7df8c9738d1152c37788de9cca3330cb2254008aee98cff66837754dfdb2902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80903d4bf89d8349b1cf96d46a4e415ec649467fe2c5a3569a4f8038d9f0705a 0.600000000000 1527036 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": 1056629, "vin": [ { "gen": { "height": 1056619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80903d4bf89d8349b1cf96d46a4e415ec649467fe2c5a3569a4f8038d9f0705a" } } ], "extra": [ 1, 214, 247, 223, 140, 151, 56, 209, 21, 44, 55, 120, 141, 233, 204, 163, 51, 12, 178, 37, 64, 8, 174, 233, 140, 255, 102, 131, 119, 84, 223, 219, 41, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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