Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 683ebc1b76aee4ea099492cb7cd8e6cb735556872e0259cfd818042a2b0667c4

Tx prefix hash: dc28cbdbad3de878afd0f118a8617427bea7810d97f57ea6853b67eb93ae857c
Tx public key: b63cddc8554162d207c774f001b90fe9d8f6a8199c108f7741812360c71717cd
Timestamp: 1701881358 Timestamp [UCT]: 2023-12-06 16:49:18 Age [y:d:h:m:s]: 01:188:03:15:08
Block: 907337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395639 RingCT/type: yes/0
Extra: 01b63cddc8554162d207c774f001b90fe9d8f6a8199c108f7741812360c71717cd02110000000533af99f4000000000000000000

1 output(s) for total of 0.604805648000 dcy

stealth address amount amount idx
00: be5b93230649c32bf35f9f8b032984f02fdb77a3a8e094023ec5e1e0a20da17d 0.604805648000 1364320 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": 907347, "vin": [ { "gen": { "height": 907337 } } ], "vout": [ { "amount": 604805648, "target": { "key": "be5b93230649c32bf35f9f8b032984f02fdb77a3a8e094023ec5e1e0a20da17d" } } ], "extra": [ 1, 182, 60, 221, 200, 85, 65, 98, 210, 7, 199, 116, 240, 1, 185, 15, 233, 216, 246, 168, 25, 156, 16, 143, 119, 65, 129, 35, 96, 199, 23, 23, 205, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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