Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e0b4325f7b1ca36500182ca297bb2eba4361adc63f9dfd6454fe971c9ccc63

Tx prefix hash: fc24e68e707276a706f812bc160f8bdd7e26dad8e34cb8215ece6fd20f6d853d
Tx public key: 9e718e95b00a2e56e0333c23af8bdfd275702ecbf1027ab08680d3f51dda9831
Timestamp: 1734451636 Timestamp [UCT]: 2024-12-17 16:07:16 Age [y:d:h:m:s]: 00:113:14:39:53
Block: 1177278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80972 RingCT/type: yes/0
Extra: 019e718e95b00a2e56e0333c23af8bdfd275702ecbf1027ab08680d3f51dda98310211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e56a3dec3fe84f6f48817f9c0cf4ccc470f2fe7475f1391b9f2e81838573635 0.600000000000 1663647 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": 1177288, "vin": [ { "gen": { "height": 1177278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e56a3dec3fe84f6f48817f9c0cf4ccc470f2fe7475f1391b9f2e81838573635" } } ], "extra": [ 1, 158, 113, 142, 149, 176, 10, 46, 86, 224, 51, 60, 35, 175, 139, 223, 210, 117, 112, 46, 203, 241, 2, 122, 176, 134, 128, 211, 245, 29, 218, 152, 49, 2, 17, 0, 0, 0, 3, 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