Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d13f62919885f31ae6bfd0e6c76d1e38da45b551efcb056ff95bd1ff382932

Tx prefix hash: dbe0a7b6f7f84ed2ae7220ef66000aaf6723cf41a7f808a637c43561ce47f548
Tx public key: 8d3a9d402fe0f5bf32c16615d982d3ce9b7e5593ab962e4e9ab06465bf4edc59
Timestamp: 1663294179 Timestamp [UCT]: 2022-09-16 02:09:39 Age [y:d:h:m:s]: 02:224:06:15:22
Block: 588849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 681610 RingCT/type: yes/0
Extra: 018d3a9d402fe0f5bf32c16615d982d3ce9b7e5593ab962e4e9ab06465bf4edc59021100000002faf35c9c000000000000000000

1 output(s) for total of 6.869085092000 dcy

stealth address amount amount idx
00: 1d3a7e69ef2b29c4cf85b433a2e19dfea65d26a6a728a9f1d747883f3f18557c 6.869085092000 1023102 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": 588859, "vin": [ { "gen": { "height": 588849 } } ], "vout": [ { "amount": 6869085092, "target": { "key": "1d3a7e69ef2b29c4cf85b433a2e19dfea65d26a6a728a9f1d747883f3f18557c" } } ], "extra": [ 1, 141, 58, 157, 64, 47, 224, 245, 191, 50, 193, 102, 21, 217, 130, 211, 206, 155, 126, 85, 147, 171, 150, 46, 78, 154, 176, 100, 101, 191, 78, 220, 89, 2, 17, 0, 0, 0, 2, 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