Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c51f62e1bea0013a00a2bc9dc3a32b477f4964a891ff23065bcaf005283a46

Tx prefix hash: fe47848e1a15424e48fcde6dd00cd0c9a4df76b9146bec9edc1094945e6a2a54
Tx public key: 608475f8c11768808bd843b941c4cb62894ac1b654041b9324ab3cb044b08b8c
Timestamp: 1698657946 Timestamp [UCT]: 2023-10-30 09:25:46 Age [y:d:h:m:s]: 01:159:05:29:07
Block: 880834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374777 RingCT/type: yes/0
Extra: 01608475f8c11768808bd843b941c4cb62894ac1b654041b9324ab3cb044b08b8c021100000004faf35c9c000000000000000000

1 output(s) for total of 0.740340176000 dcy

stealth address amount amount idx
00: 325fd553601d47ea8b06288dcfffedc5ee56204746b6745167308d2de03f4b97 0.740340176000 1336404 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": 880844, "vin": [ { "gen": { "height": 880834 } } ], "vout": [ { "amount": 740340176, "target": { "key": "325fd553601d47ea8b06288dcfffedc5ee56204746b6745167308d2de03f4b97" } } ], "extra": [ 1, 96, 132, 117, 248, 193, 23, 104, 128, 139, 216, 67, 185, 65, 196, 203, 98, 137, 74, 193, 182, 84, 4, 27, 147, 36, 171, 60, 176, 68, 176, 139, 140, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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