Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61eecfc7183d9e0c87a45752d35b2a60c3ed065f56cb8935f9b910d7ba690587

Tx prefix hash: 5a226668ed7aa89e801e1dc87bd32ddcfd029c2f228a87f675918077353d9a3c
Tx public key: 8c4ff8ef2dd63feebfe6d79bc3e8509f198439ee52dce761c8b07824fc449375
Timestamp: 1674292799 Timestamp [UCT]: 2023-01-21 09:19:59 Age [y:d:h:m:s]: 01:356:15:29:05
Block: 679481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515911 RingCT/type: yes/0
Extra: 018c4ff8ef2dd63feebfe6d79bc3e8509f198439ee52dce761c8b07824fc4493750211000000025029cbac000000000000000000

1 output(s) for total of 3.440307992000 dcy

stealth address amount amount idx
00: f98fa1a7ecc5c455791c990de95a77705cd7ebbd1d0b18a8f4ab876ef2f60df7 3.440307992000 1121462 of 0

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": 679491, "vin": [ { "gen": { "height": 679481 } } ], "vout": [ { "amount": 3440307992, "target": { "key": "f98fa1a7ecc5c455791c990de95a77705cd7ebbd1d0b18a8f4ab876ef2f60df7" } } ], "extra": [ 1, 140, 79, 248, 239, 45, 214, 63, 238, 191, 230, 215, 155, 195, 232, 80, 159, 25, 132, 57, 238, 82, 220, 231, 97, 200, 176, 120, 36, 252, 68, 147, 117, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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