Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d74f1be169f3c94f808ecbcc97485bd38aa4f74a6f9ee1551fc26d796af0c6f8

Tx prefix hash: 9838da67884ab6085eee038756d672529ba4373748fef938cb8412c5626dcef4
Tx public key: 56b3bc0d0ff0ace1f4c7cc2a0e10ad880ca4d8c8f8c57a9724e90e68d0922735
Timestamp: 1677091357 Timestamp [UCT]: 2023-02-22 18:42:37 Age [y:d:h:m:s]: 02:092:20:16:01
Block: 702710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587986 RingCT/type: yes/0
Extra: 0156b3bc0d0ff0ace1f4c7cc2a0e10ad880ca4d8c8f8c57a9724e90e68d092273502110000000174b6d784000000000000000000

1 output(s) for total of 2.881575284000 dcy

stealth address amount amount idx
00: b2c42c1c79ba6a3fc4636f4c2e193e91e4f9fe04a8b8ed323c39e90ae35f9fdc 2.881575284000 1146249 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": 702720, "vin": [ { "gen": { "height": 702710 } } ], "vout": [ { "amount": 2881575284, "target": { "key": "b2c42c1c79ba6a3fc4636f4c2e193e91e4f9fe04a8b8ed323c39e90ae35f9fdc" } } ], "extra": [ 1, 86, 179, 188, 13, 15, 240, 172, 225, 244, 199, 204, 42, 14, 16, 173, 136, 12, 164, 216, 200, 248, 197, 122, 151, 36, 233, 14, 104, 208, 146, 39, 53, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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