Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0c10dd410e95a6d17578439ac2cf1693e081e0ad759874bef3bf72a3fbeb71

Tx prefix hash: fc792022089da84e1d72c51cfca1833d261dea6dc607cc25febdca1a4ff193b5
Tx public key: 7e4f33e57b4db76e214ed6d7129bd3296a9eac8d9cf39e37c21fe7411b7433d5
Timestamp: 1681594428 Timestamp [UCT]: 2023-04-15 21:33:48 Age [y:d:h:m:s]: 01:360:06:04:02
Block: 739390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518764 RingCT/type: yes/0
Extra: 017e4f33e57b4db76e214ed6d7129bd3296a9eac8d9cf39e37c21fe7411b7433d502110000000275e3f0e9000000000000000000

1 output(s) for total of 2.178182243000 dcy

stealth address amount amount idx
00: b8c53406d9bca083461935a0fb6d4d293b292a16528165c93ec4977b199e9bd5 2.178182243000 1186239 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": 739400, "vin": [ { "gen": { "height": 739390 } } ], "vout": [ { "amount": 2178182243, "target": { "key": "b8c53406d9bca083461935a0fb6d4d293b292a16528165c93ec4977b199e9bd5" } } ], "extra": [ 1, 126, 79, 51, 229, 123, 77, 183, 110, 33, 78, 214, 215, 18, 155, 211, 41, 106, 158, 172, 141, 156, 243, 158, 55, 194, 31, 231, 65, 27, 116, 51, 213, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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