Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a09da619e573eca9da37549f1a5ce4f27a72d092db62f0d219a06619472cc96b

Tx prefix hash: 4a810955687869c858f7c3269f823ad96324a7c99a9324624533bf3fc3ef1c56
Tx public key: aa63a58b0e3e7985c1a5e61d852291cf51504cda5ab0a535d068c81e10816439
Timestamp: 1706264257 Timestamp [UCT]: 2024-01-26 10:17:37 Age [y:d:h:m:s]: 01:030:11:26:46
Block: 943650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282845 RingCT/type: yes/0
Extra: 01aa63a58b0e3e7985c1a5e61d852291cf51504cda5ab0a535d068c81e108164390211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6805ab55b827cbaaf58f329cfe8ac95e146b4f98c623fdd025d56c630646ab07 0.600000000000 1401858 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": 943660, "vin": [ { "gen": { "height": 943650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6805ab55b827cbaaf58f329cfe8ac95e146b4f98c623fdd025d56c630646ab07" } } ], "extra": [ 1, 170, 99, 165, 139, 14, 62, 121, 133, 193, 165, 230, 29, 133, 34, 145, 207, 81, 80, 76, 218, 90, 176, 165, 53, 208, 104, 200, 30, 16, 129, 100, 57, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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