Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80b2b5d5888517bedd9ea79cd4aa342fa6678747e13c58f6f70b6df5085a5633

Tx prefix hash: 1a761bef8b79e7bae742475fc2e58100eece106028b058fb5fc8b69c8c7379d9
Tx public key: 9da251e1f56d45f60f9b84359b17dd80361fef2dfc4ad6e537c63aa1d1fd7d81
Timestamp: 1688218763 Timestamp [UCT]: 2023-07-01 13:39:23 Age [y:d:h:m:s]: 01:184:11:19:02
Block: 794337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393190 RingCT/type: yes/0
Extra: 019da251e1f56d45f60f9b84359b17dd80361fef2dfc4ad6e537c63aa1d1fd7d8102110000000475e3f0e9000000000000000000

1 output(s) for total of 1.432293141000 dcy

stealth address amount amount idx
00: 0a2d39fbaf681ee8524cf806a0030dede76fc72e1bfb35854d84557eff77d281 1.432293141000 1245076 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": 794347, "vin": [ { "gen": { "height": 794337 } } ], "vout": [ { "amount": 1432293141, "target": { "key": "0a2d39fbaf681ee8524cf806a0030dede76fc72e1bfb35854d84557eff77d281" } } ], "extra": [ 1, 157, 162, 81, 225, 245, 109, 69, 246, 15, 155, 132, 53, 155, 23, 221, 128, 54, 31, 239, 45, 252, 74, 214, 229, 55, 198, 58, 161, 209, 253, 125, 129, 2, 17, 0, 0, 0, 4, 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