Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6689268024dc5fa46de7341f6913694f2a046867abc3d4b19a490c1f7a78d689

Tx prefix hash: 1a6a4c36e5d9de7bd0024ffbcb34ec351e199f2784763f5ea41896abdb242ce0
Tx public key: 6084828efbdcc3d9e732cc63900578aa2f607fedc87d2e11bd362e1dce484c8f
Timestamp: 1735426340 Timestamp [UCT]: 2024-12-28 22:52:20 Age [y:d:h:m:s]: 00:169:06:49:45
Block: 1185321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120712 RingCT/type: yes/0
Extra: 016084828efbdcc3d9e732cc63900578aa2f607fedc87d2e11bd362e1dce484c8f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f56f4cc735a544da84e7f8996cce8aae368d2dc9f0ed286e4d26558510a984b5 0.600000000000 1671788 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": 1185331, "vin": [ { "gen": { "height": 1185321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f56f4cc735a544da84e7f8996cce8aae368d2dc9f0ed286e4d26558510a984b5" } } ], "extra": [ 1, 96, 132, 130, 142, 251, 220, 195, 217, 231, 50, 204, 99, 144, 5, 120, 170, 47, 96, 127, 237, 200, 125, 46, 17, 189, 54, 46, 29, 206, 72, 76, 143, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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