Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7fee88ef1ed98f15d75c17b7d06a930adca72b0fa89fddd2c95d44e7558514f

Tx prefix hash: 73647bd30742174ed0d66ba6924b98eb9f754088486dd53ff860dea59d042d3e
Tx public key: ca12ed80307fa67dd3004977b2377cd1112229d7cb3ebc4b3607ebf9df8db15c
Timestamp: 1724108509 Timestamp [UCT]: 2024-08-19 23:01:49 Age [y:d:h:m:s]: 00:266:05:42:40
Block: 1091623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190166 RingCT/type: yes/0
Extra: 01ca12ed80307fa67dd3004977b2377cd1112229d7cb3ebc4b3607ebf9df8db15c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e0796404f67b1f631aa979e410fbea1fe58ae8c4bcb52d3f1273c72ebc1a19 0.600000000000 1566256 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": 1091633, "vin": [ { "gen": { "height": 1091623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e0796404f67b1f631aa979e410fbea1fe58ae8c4bcb52d3f1273c72ebc1a19" } } ], "extra": [ 1, 202, 18, 237, 128, 48, 127, 166, 125, 211, 0, 73, 119, 178, 55, 124, 209, 17, 34, 41, 215, 203, 62, 188, 75, 54, 7, 235, 249, 223, 141, 177, 92, 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