Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d1670f694104f8ad5b65f52c46e7a272b7bb11f035ccb9f90c0da2143d8762

Tx prefix hash: 30a618bf8ed9f136cd25a7f51eb05fccd10d63afc0aa834c085d72f73cf5cf40
Tx public key: def57bf7e69d7d5277cfbd307f7e797aa60903e8d25a875638f8063a4586d460
Timestamp: 1712688165 Timestamp [UCT]: 2024-04-09 18:42:45 Age [y:d:h:m:s]: 01:236:13:57:57
Block: 996916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427808 RingCT/type: yes/0
Extra: 01def57bf7e69d7d5277cfbd307f7e797aa60903e8d25a875638f8063a4586d46002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fc11aa866befcfef394129e88df160a36278f26e43247a39e1dfe04b5061243 0.600000000000 1457344 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": 996926, "vin": [ { "gen": { "height": 996916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fc11aa866befcfef394129e88df160a36278f26e43247a39e1dfe04b5061243" } } ], "extra": [ 1, 222, 245, 123, 247, 230, 157, 125, 82, 119, 207, 189, 48, 127, 126, 121, 122, 166, 9, 3, 232, 210, 90, 135, 86, 56, 248, 6, 58, 69, 134, 212, 96, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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