Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba70ee2355cee6d23b65e3810ed3d0720241f4598e7e5385f0a335396480c57

Tx prefix hash: 351f7ee11ef9bd3f7a594a92e39d11b2cd4b83c4639770a78b5208c81eee7385
Tx public key: 87c172966604b35ee2de1760aa7eb128a1b87ef3ae01f13c90d00a1e7b963963
Timestamp: 1696694672 Timestamp [UCT]: 2023-10-07 16:04:32 Age [y:d:h:m:s]: 02:032:17:50:39
Block: 864545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543031 RingCT/type: yes/0
Extra: 0187c172966604b35ee2de1760aa7eb128a1b87ef3ae01f13c90d00a1e7b96396302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.838307903000 dcy

stealth address amount amount idx
00: 00210b507680f60ebdc43f9274ec52c34dc531b3e5fe8e27b5484985bf77bec3 0.838307903000 1319061 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": 864555, "vin": [ { "gen": { "height": 864545 } } ], "vout": [ { "amount": 838307903, "target": { "key": "00210b507680f60ebdc43f9274ec52c34dc531b3e5fe8e27b5484985bf77bec3" } } ], "extra": [ 1, 135, 193, 114, 150, 102, 4, 179, 94, 226, 222, 23, 96, 170, 126, 177, 40, 161, 184, 126, 243, 174, 1, 241, 60, 144, 208, 10, 30, 123, 150, 57, 99, 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