Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd8c0fd15b6e606a4f5691b06e4e1c1af15c9d0b040e5abfee7f663e677756d1

Tx prefix hash: fc56c5d212cc5643670f576ef884b312a4fd8dcee09cf66d8b6742b74bc71ff6
Tx public key: 4310d837df89f4afc775077d84a7c925d53b962f942c514065ba65af9fbd0e5a
Timestamp: 1716912014 Timestamp [UCT]: 2024-05-28 16:00:14 Age [y:d:h:m:s]: 01:162:08:57:05
Block: 1031971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374606 RingCT/type: yes/0
Extra: 014310d837df89f4afc775077d84a7c925d53b962f942c514065ba65af9fbd0e5a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b07c15be3eff8805b4611e54b03cc53c19bfd9e3f9a3173ef6020e3d5ad050 0.600000000000 1500420 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": 1031981, "vin": [ { "gen": { "height": 1031971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b07c15be3eff8805b4611e54b03cc53c19bfd9e3f9a3173ef6020e3d5ad050" } } ], "extra": [ 1, 67, 16, 216, 55, 223, 137, 244, 175, 199, 117, 7, 125, 132, 167, 201, 37, 213, 59, 150, 47, 148, 44, 81, 64, 101, 186, 101, 175, 159, 189, 14, 90, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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