Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 135caeb848e98119be8a9d1962a2aa7363f4b97e33fdb3bd406a27feb63774dd

Tx prefix hash: 1026e6480c2b7615676614d81b008eef45947fa690022a07a9dafea77583c30e
Tx public key: a66dfa7405e6c67a9fcf734fa76f857b51d149008a05f74fc7ae3df316e6dd8d
Timestamp: 1712899469 Timestamp [UCT]: 2024-04-12 05:24:29 Age [y:d:h:m:s]: 01:014:06:27:37
Block: 998669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271181 RingCT/type: yes/0
Extra: 01a66dfa7405e6c67a9fcf734fa76f857b51d149008a05f74fc7ae3df316e6dd8d02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3d439aca809e0b36d9118c5157c0d11ead67f297fd8ea1825e545ef4a394d6 0.600000000000 1459121 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": 998679, "vin": [ { "gen": { "height": 998669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3d439aca809e0b36d9118c5157c0d11ead67f297fd8ea1825e545ef4a394d6" } } ], "extra": [ 1, 166, 109, 250, 116, 5, 230, 198, 122, 159, 207, 115, 79, 167, 111, 133, 123, 81, 209, 73, 0, 138, 5, 247, 79, 199, 174, 61, 243, 22, 230, 221, 141, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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